| 2 |
Approval of Agenda |
|
| R1-2003250 |
Draft Agenda of RAN1#101-e meeting |
RAN1 Chair |
| R1-2003585 |
Additional Guidelines for RAN1#101 e-Meeting Management |
RAN1 Chair |
| R1-2003586 |
RAN1#101-e Meeting Invitation, Timelines, Scope, Process |
RAN1 Chair, ETSI MCC |
| R1-2004689 |
RAN1#101-e Meeting Invitation, Timelines, Scope, Process |
RAN1 Chair, ETSI MCC |
| R1-2004695 |
RAN1#101-e Meeting Invitation, Timelines, Scope, Process |
RAN1 Chair, ETSI MCC |
| R1-2004698 |
Additional Guidelines for RAN1#101 e-Meeting Management |
RAN1 Chair |
| 4 |
Approval of Minutes from previous meeting |
|
| R1-2003251 |
Report of RAN1#100bis-e meeting |
ETSI MCC |
| 5 |
Incoming Liaison Statements |
|
| R1-2003252 |
LS to RAN1 on Guard Symbols in IAB |
RAN2, Samsung |
| R1-2003253 |
LS on the 3GPP work on the NR sidelink |
5GAA WG4, Volkswagen |
| R1-2003254 |
Reply LS on consistent Uplink LBT failure detection mechanism |
RAN2, Nokia |
| R1-2003255 |
LS on Cast type indication and MAC agreements |
RAN2 LG Electronics |
| R1-2003256 |
LS to RAN1 to check the view on sidelink |
RAN2, Huawei |
| R1-2003257 |
LS on RLF Agreements |
RAN2, InterDigital |
| R1-2003258 |
LS on UE capability |
RAN2, OPPO |
| R1-2003259 |
LS on Intra-UE Prioritization |
RAN2, Nokia |
| R1-2003260 |
LS on RAN2 DCP Open Issues |
RAN2, InterDigital |
| R1-2003261 |
LS to RAN1 on agreements related to 2-step RACH |
RAN2, ZTE |
| R1-2003262 |
LS reply on uplink power control for NR-NR Dual-Connectivity |
RAN2, Apple |
| R1-2003263 |
Reply LS on UL LBT failure recovery for the target cell |
RAN2, InterDigital |
| R1-2003264 |
Response LS on SRS and SSB configuration for NR Positioning |
RAN2, Intel |
| R1-2003265 |
LS on support for UL NR E-CID |
RAN3, Nokia |
| R1-2003266 |
Reply LS on TDD pattern exchange for NR-DC power control |
RAN3, vivo |
| R1-2003267 |
LS on secondary DRX group for FR1+FR2 CA |
RAN4, Apple |
| R1-2003268 |
Reply LS on CLI measurement and reporting |
RAN4, LG Electronics |
| R1-2003269 |
LS on inter-frequency measurement requirement without MG |
RAN4, Huawei |
| R1-2003270 |
LS on pre-emption on CSI-RS for L3 measurement |
RAN4, MediaTek |
| R1-2003271 |
LS on UE declaring beam failure due to LBT failures during active TCI switching |
RAN4, Ericsson |
| R1-2003272 |
LS on timing reference cell adjustment under NR-U |
RAN4, ZTE |
| R1-2003273 |
LS on transmit power of CSI-RS across different occasions |
RAN4, Huawei |
| R1-2003274 |
LS on NR-U SSB monitoring capabilities |
RAN4, Nokia |
| R1-2003275 |
LS on RAN4 IAB-MT feature list agreement |
RAN4, Qualcomm |
| R1-2003276 |
LS on Rel-16 RAN4 UE features lists for NR and LTE |
RAN4, NTT DOCOMO |
| R1-2003277 |
LS on SCell dormancy requirement scope |
RAN4, Ericsson |
| R1-2003278 |
LS on UE capability for Tx switching between two uplink carriers |
RAN4, Apple |
| R1-2003279 |
Reply LS on NR Positioning gNB measurement report range and granularity |
RAN4, Intel |
| R1-2003280 |
LS on report mapping for UE positioning measurement |
RAN4, Huawei |
| R1-2003345 |
Draft reply LS on Intra-UE Prioritization |
ZTE |
| R1-2003347 |
Discussion on Intra-UE Prioritization |
vivo |
| R1-2003348 |
Draft reply LS on Intra-UE Prioritization |
vivo |
| R1-2003349 |
Discussion on premption on CSI-RS for L3 measurement |
vivo |
| R1-2003350 |
DRAFT Reply LS on Cast type indication |
vivo |
| R1-2003351 |
DRAFT Reply LS to on sidelink HARQ process ID and RRC parameters |
vivo |
| R1-2003352 |
DraftT Reply LS on Guard Symbols in IAB |
vivo |
| R1-2003353 |
Discussion on DCP Open Issues |
vivo |
| R1-2003354 |
Transmit power of CSI-RS across different occasions |
vivo |
| R1-2003355 |
Discussion on NR-U SSB monitoring capabilities |
vivo |
| R1-2003484 |
Draft reply LS on DCP Open Issues |
ZTE |
| R1-2003485 |
Discussion on collision between DCP and RAR |
ZTE |
| R1-2003542 |
About reply LS on IAB guard symbols |
ZTE, Sanechips |
| R1-2003543 |
About reply LS for cell-specific signals/channels configurations in IAB |
ZTE, Sanechips |
| R1-2003572 |
Discussion on RAN2 LS on RLF Agreements |
LG Electronics |
| R1-2003583 |
Discussion on RAN2 LS on Intra-UE Prioritization |
Nokia, Nokia Shanghai Bell |
| R1-2003584 |
[Draft] Reply LS on Intra-UE Prioritization |
Nokia |
| R1-2003587 |
Draft LS reply on DCP open issues |
CATT |
| R1-2003588 |
Draft LS reply on checking the view on sidelink |
CATT |
| R1-2003589 |
Draft LS reply on Intra-UE Prioritization |
CATT |
| R1-2003697 |
Discussion on RAN4 LS on pre-emption of CSI-RS for L3 measurement |
MediaTek Inc. |
| R1-2003712 |
About reply LS to RAN2 on cast type indication |
ZTE, Sanechips |
| R1-2003836 |
Draft reply LS on NR-U SSB monitoring capabilities |
ZTE |
| R1-2003837 |
Draft reply LS on transmit power of CSI-RS across different occasions |
ZTE |
| R1-2003838 |
Draft reply LS on UE declaring beam failure due to LBT failures during active TCI switching |
ZTE |
| R1-2003852 |
Draft reply LS on RAN2 DCP open issues |
Samsung |
| R1-2003853 |
Draft Response LS on NR-U SSB monitoring capabilities |
Samsung |
| R1-2004007 |
Discussion on RAN2 reply LS on consistent uplink LBT failure detection mechanism for NR-U |
LG Electronics |
| R1-2004008 |
Discussion on RAN4 LS on transmit power of CSI-RS across different occasions for NR-U |
LG Electronics |
| R1-2004009 |
Discussion on RAN4 LS on NR-U SSB monitoring capabilities |
LG Electronics |
| R1-2004067 |
Discussion on NR sidelink cast type indication |
OPPO |
| R1-2004068 |
Discussion on RAN1's view on NR sidelink |
OPPO |
| R1-2004069 |
Discussion on maximum data rate of NR sidelink |
OPPO |
| R1-2004092 |
Discussion on UE declaring beam failure due to LBT failures during active TCI switching |
OPPO |
| R1-2004093 |
Discusson on transmit power of CSI-RS across different occasions |
OPPO |
| R1-2004094 |
Discussion on NR-U SSB monitoring capabilities |
OPPO |
| R1-2004095 |
[Draft] Reply to LS on NR-U SSB monitoring capabilities |
OPPO |
| R1-2004113 |
Reply LS on RAN2 DCP Open Issues |
OPPO |
| R1-2004123 |
Discussion on Intra-UE prioritization |
OPPO |
| R1-2004124 |
[Draft] Rely LS on Intra UE prioritization |
OPPO |
| R1-2004126 |
Discussions on guard symbols in IAB |
LG Electronics |
| R1-2004127 |
Draft Reply LS on IAB-MT feature list |
LG Electronics |
| R1-2004128 |
Draft Reply LS on pre-emption on CSI-RS for L3 measurement |
LG Electronics |
| R1-2004129 |
Discussion on RAN3 LS on support for UL NR E-CID from |
LG Electronics |
| R1-2004343 |
Discussion on LS from RAN4 on IAB-MT feature list |
LG Electronics |
| R1-2004428 |
Response to LS on Conflicting Configurations |
Ericsson Inc. |
| R1-2004433 |
Discussion on Intra-UE prioritization |
Qualcomm Incorporated |
| R1-2004502 |
Discussion on the RAN2 Reply LS on consistent Uplink LBT failure detection mechanism |
Nokia, Nokia Shanghai Bell |
| R1-2004513 |
[DRAFT] Reply LS on transmit power of CSI-RS across different occasions |
Nokia |
| R1-2004571 |
LS on positioning SRS during DRX inactive time |
RAN2, Huawei |
| R1-2004581 |
Pre-emption of CSI-RS for L3 mobility |
Nokia, Nokia Shanghai Bell |
| R1-2004599 |
[Draft] LS reply to RAN2 on Cast type indication and MAC agreements |
Huawei |
| R1-2004600 |
[Draft] LS reply to RAN2 on check the view on sidelink |
Huawei |
| R1-2004601 |
[Draft] LS reply to RAN2 on UE capability |
Huawei |
| R1-2004618 |
[Draft] Reply LS on Guard Symbols in IAB |
Huawei |
| R1-2004619 |
Discussion on Guard Symbols in IAB |
Huawei, HiSilicon |
| R1-2004620 |
[Draft] Reply LS on cell-specific signals/channel configurations |
Huawei |
| R1-2004621 |
Discussions on cell-specific signals/channel configurations of child IAB-DU |
Huawei, HiSilicon |
| R1-2004624 |
[DRAFT] Reply LS on transmit power of CSI-RS across different occasions |
Huawei |
| R1-2004625 |
Draft reply LS on RAN2 DCP Open Issues |
Huawei |
| R1-2004626 |
Discussion on the collision between DCP and RAR addressed to C-RNTI |
Huawei, HiSilicon |
| R1-2004627 |
[Draft] Reply LS on Conflicting configurations |
Huawei |
| R1-2004629 |
[Draft] Reply LS on pre-emption on CSI-RS for L3 measurement |
Huawei |
| R1-2004665 |
LS on Conflicting configurations |
RAN2, Huawei |
| R1-2004680 |
RAN1#101-e preparation phase on LSs |
RAN1 Chair |
| R1-2004681 |
RAN1#101-e preparation phase output on LSs |
RAN1 Chair |
| R1-2004685 |
LS on cell-specific signals/channel configurations |
RAN3, ZTE |
| R1-2004693 |
LS on Extending current NR operation to 71 GHz |
MulteFire AllianceTSG, InterDigital, Nokia |
| R1-2004808 |
Reply LS on Conflicting configurations |
RAN1, Huawei |
| R1-2004809 |
Summary of [101-e-5LS-01] discussions for a reply LS on Conflicting configurations |
Moderator (Huawei) |
| R1-2004810 |
Reply LS on pre-emption on CSI-RS for L3 measurement |
RAN1, MediaTek |
| R1-2004811 |
Summary of [101-e-5LS-02] discussions for a reply LS on pre-emption on CSI-RS for L3 measurement |
Moderator (MediaTek) |
| R1-2004922 |
LS Reply to RAN1 on UL PC for NR-DC |
RAN2, Apple |
| R1-2004935 |
Reply LS on RVID selection for CG-PUSCH |
RAN2, Qualcomm |
| R1-2004936 |
Reply LS on Rel-16 UE feature lists |
RAN2, Intel |
| R1-2005045 |
Reply LS on sidelink HARQ operations |
RAN2, LG electronics |
| R1-2005070 |
Reply LS on updated Rel-16 LTE and NR parameter lists |
RAN2, Ericsson |
| 5.1 |
RAN1 Aspects for RF requirements for NR frequency range 1 (FR1) |
|
| R1-2003332 |
Remaining Issues on Support of Tx Switching between Two Uplink Carriers |
ZTE |
| R1-2003356 |
Remaining issues on UL carrier switch |
vivo |
| R1-2003590 |
Remaining issues on UL Tx switching |
CATT |
| R1-2003830 |
Summary of uplink Tx switching |
Moderator (China Telecom) |
| R1-2003831 |
Remaining issues on uplink Tx switching |
China Telecom |
| R1-2004356 |
RAN1 aspects of UL Tx switching |
Ericsson |
| R1-2004376 |
Discussion on Tx Switching between Two Uplink Carriers |
OPPO |
| R1-2004434 |
Remaining issues for 1Tx-2Tx switching |
Qualcomm Incorporated |
| R1-2004501 |
Remaining open issues on Tx switching between two uplink carriers |
Nokia, Nokia Shanghai Bell |
| R1-2004603 |
Discussion on the remaining problems of supporting Tx switching between two uplink carriers |
Huawei, HiSilicon |
| R1-2004699 |
Summary#2 of uplink Tx switching |
Moderator (China Telecom) |
| R1-2004986 |
[101-e-LS-TxSwitching-01] Email discussion/approval on remaining issues for inter-band UL CA |
Moderator (China Telecom) |
| R1-2004987 |
[101-e-LS-TxSwitching-02] Email discussion/approval on remaining issues for EN-DC |
Moderator (China Telecom) |
| R1-2004988 |
[101-e-LS-TxSwitching-03] Email discussion/approval on other issues for uplink Tx switching |
Moderator (China Telecom) |
| R1-2005120 |
Introduction of switched uplink operation |
Nokia, Nokia Shanghai Bell |
| 5.2 |
RAN1 Aspects for RF Requirement Enhancements for FR2 |
|
| R1-2003465 |
Enhancement on FR2 MPE mitigation |
ZTE |
| 6.1 |
Maintenance of E-UTRA Releases 8–15 |
|
| R1-2004006 |
Clarification on PRACH Collision Handling for NB-IoT |
MediaTek Inc. |
| R1-2004162 |
Correction on MBSFN region start symbol index of an MBSFN subframe |
Huawei, HiSilicon |
| R1-2004289 |
Draft CR on clarification of RSS transmission |
ZTE,Sanechips, Qualcomm Incorporated |
| R1-2004290 |
Draft CR on scrambling initialization for sub-PRB PUSCH |
ZTE, Sanechips, |
| R1-2004678 |
RAN1#101-e preparation phase on Maintenance of E-UTRA Releases 8-15 |
Ad-Hoc Chair (Ericsson) |
| R1-2004679 |
RAN1#101-e preparation phase output on Maintenance of E-UTRA Releases 8-15 |
Ad-Hoc Chair (Ericsson) |
| R1-2004785 |
CR on clarification of RSS transmission |
ZTE, Sanechips, Qualcomm Incorporated |
| R1-2004786 |
CR on clarification of RSS transmission |
ZTE, Sanechips, Qualcomm Incorporated |
| R1-2004787 |
CR on scrambling initialization for sub-PRB PUSCH |
ZTE , Sanechips, Qualcomm Incorporated, Ericsson |
| R1-2004788 |
CR on scrambling initialization for sub-PRB PUSCH |
ZTE , Sanechips, Qualcomm Incorporated, Ericsson |
| R1-2004863 |
Correction on MBSFN region start symbol index of an MBSFN subframe |
Huawei, HiSilicon |
| R1-2004864 |
Correction on MBSFN region start symbol index of an MBSFN subframe |
Huawei, HiSilicon |
| R1-2004865 |
Correction on MBSFN region start symbol index of an MBSFN subframe |
Huawei, HiSilicon |
| R1-2004866 |
Correction on MBSFN region start symbol index of an MBSFN subframe |
Huawei, HiSilicon |
| R1-2004867 |
Correction on MBSFN region start symbol index of an MBSFN subframe |
Huawei, HiSilicon |
| R1-2004882 |
Summary of Email Discussion on PRACH Collision Handling for NB-IoT in RAN1#101-e |
Ad-Hoc Chair (Ericsson) |
| R1-2004917 |
Correction on MBSFN region start symbol index of an MBSFN subframe |
Huawei, HiSilicon |
| R1-2005088 |
Session notes for 6.1 (Maintenance of E-UTRA Releases 8-15) |
Ad-Hoc Chair (Ericsson) |
| R1-2005168 |
Corrections for Rel-16 NB-IoT features in 36.211 |
Ericsson |
| R1-2005169 |
Corrections to LTE terrestrial broadcast |
Ericsson |
| R1-2005170 |
Corrections to Rel-16 LTE-MTC features in 36.211 |
Ericsson |
| R1-2005171 |
Corrections to DL MIMO efficiency enhancements for LTE |
Ericsson |
| R1-2005172 |
Miscellaneous corrections for Rel-16 NB-IoT features in 36.212 |
Futurewei |
| R1-2005173 |
Miscellaneous corrections for Rel-16 DL MIMO EE features in 36.212 |
Futurewei |
| R1-2005174 |
Miscellaneous corrections for Rel-16 eMTC features in 36.212 |
Futurewei |
| R1-2005175 |
Correction to define the values of SPS activation/release in DCI format 5A |
Futurewei |
| R1-2005176 |
Correction to define the values of SPS activation/release in DCI format 5A |
Futurewei |
| R1-2005177 |
Correction to define the values of SPS activation/release in DCI format 5A |
Futurewei |
| R1-2005178 |
Corrections to Additional enhancements for NB-IoT |
Motorola Mobility |
| R1-2005179 |
Corrections to LTE-based 5G terrestrial broadcast |
Motorola Mobility |
| R1-2005180 |
Corrections to Additional MTC Enhancements for LTE |
Motorola Mobility |
| R1-2005181 |
Corrections to DL MIMO efficiency enhancements for LTE |
Motorola Mobility |
| R1-2005183 |
Corrections to LTE terrestrial broadcast |
Ericsson |
| R1-2005184 |
Corrections to DL MIMO efficiency enhancements for LTE |
Ericsson |
| R1-2005189 |
Corrections to LTE-based 5G terrestrial broadcast |
Motorola Mobility |
| R1-2005190 |
Corrections to DL MIMO efficiency enhancements for LTE |
Motorola Mobility |
| 6.2 |
Maintenance of E-UTRA Release 16 |
|
| R1-2005082 |
Session notes for 6.2.1 (Maintenance of Additional MTC Enhancements) and 6.2.2 (Maintenance of Additional Enhancements for NB-IoT) |
Ad-hoc Chair (Samsung) |
| R1-2005187 |
Correction to remove the term ‘compact’ for DCI format 6-1A |
Futurewei |
| 6.2.1.1 |
UE-group wake-up signal |
|
| R1-2003790 |
Clarification of group WUS for MTC |
ZTE |
| R1-2004167 |
Corrections on UE-group wake-up signal |
Huawei, HiSilicon |
| R1-2004654 |
Corrections for UE-group wake-up signal for LTE-MTC |
Ericsson |
| R1-2004672 |
Clarification of group WUS for MTC |
ZTE |
| R1-2004684 |
FL Summary of Maintenance for group MWUS |
Moderator (Qualcomm) |
| R1-2004888 |
FL summary of email discussion [101-e-LTE-eMTC5-WUS-01] |
Moderator (Qualcomm Incorporated) |
| R1-2004952 |
LS on RAN1 clarification on MWUS frequency allocation |
RAN1, Ericsson |
| 6.2.1.2 |
Support for transmission in preconfigured UL resources |
|
| R1-2003539 |
Corrections on transmission in preconfigured UL resources |
Huawei, HiSilicon |
| R1-2003781 |
Support for transmission in preconfigured UL resources |
Qualcomm Incorporated |
| R1-2003791 |
Remaining issues for transmission in preconfigured UL resources for MTC |
ZTE |
| R1-2004655 |
Corrections for Preconfigured UL resources for LTE-MTC |
Ericsson |
| R1-2004690 |
LTE-M Preconfigured UL resources feature lead summary #1 RAN1 #101-e |
Moderator (Sierra Wireless) |
| R1-2004691 |
LTE-M Preconfigured UL resources feature lead summary #2 RAN1 #101-e |
Moderator (Sierra Wireless) |
| R1-2004800 |
Feature lead email summary [101-e-LTE-eMTC5-PUR-01] |
Moderator (Sierra Wireless) |
| R1-2004801 |
Feature lead email summary [101-e-LTE-eMTC5-PUR-02] |
Moderator (Sierra Wireless) |
| R1-2004802 |
Feature lead email summary [101-e-LTE-eMTC5-PUR-03] |
Moderator (Sierra Wireless) |
| 6.2.1.3 |
Scheduling of multiple DL/UL transport blocks |
|
| R1-2003540 |
Corrections on scheduling of multiple transport blocks |
Huawei, HiSilicon |
| R1-2003782 |
Scheduling of multiple DL/UL transport blocks |
Qualcomm Incorporated |
| R1-2003792 |
Remaining issues on scheduling enhancement for MTC |
ZTE |
| R1-2004656 |
Corrections for Multi-TB scheduling for LTE-MTC |
Ericsson |
| R1-2004696 |
Feature lead summary #1 for Multi-TB scheduling for LTE-MTC |
Moderator (Ericsson) |
| R1-2004729 |
Feature lead summary #2 for Multi-TB scheduling for LTE-MTC |
Moderator (Ericsson) |
| R1-2004782 |
TP on scheduling gap for multicast |
ZTE |
| R1-2004844 |
Text proposal on clarification of sub-PRB symbol counter reset |
Huawei, HiSilicon |
| R1-2004876 |
TP for TDD HARQ-ACK bundling |
Qualcomm Incorporated |
| R1-2004877 |
TP for SPS |
Qualcomm Incorporated |
| 6.2.1.4 |
Coexistence of LTE-MTC with NR |
|
| R1-2003793 |
Remaining issues on LTE-MTC resource reservation |
ZTE |
| R1-2004165 |
Corrections on eMTC co-existence with NR |
Huawei, HiSilicon |
| R1-2004657 |
TP for 36.211 on DL DMRS handling for LTE-MTC resource reservation |
Ericsson |
| R1-2004697 |
Feature lead summary #1 for NR coexistence performance improvements for LTE-MTC |
Moderator (Ericsson) |
| R1-2004730 |
Feature lead summary #2 for NR coexistence performance improvements for LTE-MTC |
Moderator (Ericsson) |
| R1-2004783 |
TP for 36213 on resource reservation in special subframes |
ZTE |
| 6.2.1.7 |
CE mode A and B improvements for non-BL UEs |
|
| R1-2003794 |
Clarification of DCI Format 6-1B for direct indication |
ZTE |
| R1-2004020 |
FL summary of CE mode A and B improvements for non-BL UEs |
Moderator (LG Electronics) |
| 6.2.1.10 |
Other |
|
| R1-2004291 |
Higher layer parameter alignment issues in Rel-16 MTC enhancement |
ZTE |
| R1-2004658 |
On L1 parameter name corrections for Rel-16 LTE-MTC |
Ericsson |
| 6.2.2.1 |
UE-group wake-up signal |
|
| R1-2003795 |
Clarification of group WUS for NB-IoT |
ZTE |
| R1-2004164 |
Corrections on UE-group wake-up signal |
Huawei, HiSilicon |
| R1-2004673 |
Clarification of group WUS for NB-IoT |
ZTE |
| R1-2004694 |
Feature lead summary #1 of Group WUS for NB-IoT |
Moderator (Ericsson) |
| R1-2004832 |
Feature lead summary #2 of Group WUS for NB-IoT |
Moderator (Ericsson) |
| R1-2004902 |
TP for 36.211 on common WUS for LTE-MTC and NB-IoT |
Moderator (Ericsson) |
| 6.2.2.2 |
Support for transmission in preconfigured UL resources |
|
| R1-2003536 |
Corrections on transmission in preconfigured UL resources |
Huawei, HiSilicon |
| R1-2003783 |
Support for transmission in preconfigured UL resources |
Qualcomm Incorporated |
| R1-2003796 |
Remaining issues for transmission in preconfigured UL resources for NB-IoT |
ZTE |
| R1-2004533 |
Feature lead summary #1 on transmission in pre-configured UL resources for NB-IoT |
Moderator (Huawei) |
| R1-2004534 |
Feature lead summary #2 on transmission in pre-configured UL resources for NB-IoT |
Moderator (Huawei) |
| R1-2004659 |
Corrections for Preconfigured UL resources for NB-IoT |
Ericsson |
| R1-2004889 |
Feature lead summary #1 on [101-e-LTE-NB_IoTenh3-PUR-01] |
Moderator (Huawei) |
| R1-2004890 |
Text Proposal for Issue#1 in [101-e-LTE-NB_IoTenh3-PUR-01] |
Moderator (Huawei) |
| R1-2004891 |
Text Proposal for Issue#2 in [101-e-LTE-NB_IoTenh3-PUR-01] |
Moderator (Huawei) |
| R1-2004892 |
Feature lead summary #1 on [101-e-LTE-NB_IoTenh3-PUR-02] |
Moderator (Huawei) |
| R1-2004893 |
Text Proposal for Issue#6 in [101-e-LTE-NB_IoTenh3-PUR-02] |
Moderator (Huawei) |
| R1-2004894 |
Text Proposal for Issue#5 in [101-e-LTE-NB_IoTenh3-PUR-02] |
Moderator (Huawei) |
| R1-2004895 |
Feature lead summary #1 on [101-e-LTE-NB_IoTenh3-PUR-03] |
Moderator (Huawei) |
| R1-2004896 |
Text Proposal for Issue#3 in [101-e-LTE-NB_IoTenh3-PUR-03] |
Moderator (Huawei) |
| R1-2004897 |
Text Proposal (RRC) for Issue#4 in [101-e-LTE-NB_IoTenh3-PUR-03] |
Moderator (Huawei) |
| R1-2004898 |
Text Proposal (PHY) for Issue#4 in [101-e-LTE-NB_IoTenh3-PUR-03] |
Moderator (Huawei) |
| 6.2.2.3 |
Scheduling of multiple DL/UL transport blocks |
|
| R1-2003537 |
Corrections on scheduling of multiple DL/UL transport blocks |
Huawei, HiSilicon |
| R1-2003797 |
Remaining issues on scheduling enhancement for NB-IoT |
ZTE |
| R1-2004670 |
Feature lead summary #1 on multiple TB scheduling for NB-IoT |
Moderator (ZTE) |
| R1-2004671 |
Feature lead summary #2 on multiple TB scheduling for NB-IoT |
Moderator (ZTE) |
| R1-2004923 |
TP on RV rule for the second TB |
Moderator (ZTE) |
| R1-2004956 |
TP on DCI format N1 for TS 36.212 |
Moderator (ZTE) |
| 6.2.2.4 |
Coexistence of NB-IoT with NR |
|
| R1-2003538 |
Corrections on coexistence of NB-IoT with NR |
Huawei, HiSilicon |
| R1-2003798 |
Remaining issues on NB-IoT resource reservation |
ZTE |
| R1-2004704 |
Feature lead summary on coexistence of NB-IoT with NR |
Moderator (Huawei) |
| R1-2004842 |
Feature lead summary on 101-e-LTE-NB_IoTenh3-Coex-NR-01 |
Moderator (Huawei) |
| R1-2004843 |
Text proposal on DCI size alignment |
Moderator (Huawei) |
| 6.2.2.7 |
Other |
|
| R1-2004292 |
Higher layer parameter alignment issues in Rel-16 NB-IoT enhancement |
ZTE |
| R1-2004660 |
On L1 parameter name corrections for Rel-16 NB-IoT |
Ericsson |
| R1-2004705 |
Feature lead summary on RRC parameters of NB-IoT |
Moderator (Huawei) |
| 6.2.3 |
Maintenance of DL MIMO efficiency enhancements for LTE |
|
| R1-2004168 |
Work item summary for DL MIMO efficiency enhancements for LTE |
Huawei |
| R1-2005083 |
Session notes for 6.2.3 (Maintenance of DL MIMO efficiency enhancements for LTE) |
Ad-hoc Chair (Samsung) |
| 6.2.3.1.1 |
Additional SRS symbols |
|
| R1-2003466 |
Maintenance of additional SRS symbols |
ZTE |
| R1-2003541 |
Corrections on additional SRS symbols |
Huawei, HiSilicon |
| R1-2003723 |
Corrections to additional SRS |
Intel Corporation |
| R1-2003784 |
Additional SRS symbols |
Qualcomm Incorporated |
| R1-2003818 |
Additional SRS symbols |
Lenovo, Motorola Mobility |
| R1-2003925 |
Text proposals on additional SRS symbols |
LG Electronics |
| R1-2003937 |
Remaining details of additional SRS symbols |
Nokia, Nokia Shanghai Bell |
| R1-2004431 |
Maintenance on additional SRS symbols |
Ericsson |
| R1-2004706 |
Feature summary on LTE DL MIMO efficiency enhancement |
Moderator (Huawei) |
| R1-2004845 |
Feature summary on 101-e-LTE-LTE_DL_MIMO_EE-01 |
Moderator (Huawei) |
| R1-2004846 |
Feature summary on 101-e-LTE-LTE_DL_MIMO_EE-02 |
Moderator (Huawei) |
| R1-2004847 |
Text proposal on additional SRS for dual connectivity |
Moderator (Huawei) |
| R1-2004848 |
Text proposal on additional SRS for carrier based switching |
Moderator (Huawei) |
| R1-2004849 |
Text proposal on additional SRS for LAA eMTC |
Moderator (Huawei) |
| R1-2004850 |
Text proposal on indexing of additional SRS symbols |
Moderator (Huawei) |
| 6.2.4 |
Maintenance of LTE-based 5G Terrestrial Broadcast |
|
| R1-2004200 |
Corrections to LTE-based 5G terrestrial broadcast |
Nokia, Nokia Shanghai Bell |
| R1-2004687 |
Summary of issues for LTE-based 5G terrestrial broadcast |
Moderator (Qualcomm) |
| R1-2004755 |
Corrections to LTE-based 5G terrestrial broadcast |
Nokia, Nokia Shanghai Bell |
| R1-2005089 |
Session notes for 6.2.4 (Maintenance of LTE-based 5G Terrestrial Broadcast) |
Ad-Hoc Chair (Ericsson) |
| 6.2.4.1 |
New numerology(ies) for PMCH for support of rooftop reception |
|
| R1-2003337 |
Control region for the new numerologies of LTE-based 5G terrestrial broadcast |
ZTE |
| R1-2003535 |
Corrections to 36.211 for the 0.37 kHz subcarrier spacing MBSFN |
Huawei, HiSilicon |
| R1-2003785 |
Support of longer numerologies for rooftop reception |
Qualcomm Incorporated |
| R1-2004667 |
Control region for the new numerologies of LTE-based 5G terrestrial broadcast |
ZTE, ABS |
| R1-2004878 |
Summary of 101-e-LTE_TerrBcast-02 |
Moderator (Qualcomm Incorporated) |
| R1-2004879 |
Summary of 101-e-LTE_TerrBcast-01 |
Moderator (Qualcomm Incorporated) |
| R1-2004880 |
[DRAFT] LS on categories for terrestrial broadcast |
Qualcomm Incorporated |
| R1-2004912 |
LS on categories for terrestrial broadcast |
RAN1, Qualcomm Incorporated |
| 6.2.4.2 |
Necessity and detailed enhancements to the physical channels and signals in the CAS |
|
| R1-2003786 |
Corrections for CAS reception |
Qualcomm Incorporated |
| 6.2.4.3 |
New numerology for support of mobility of up to 250km/h |
|
| R1-2004163 |
Corrections to 36.211 for the 2.5 kHz subcarrier spacing MBSFN |
Huawei, HiSilicon |
| 6.2.5 |
LTE Rel-16 UE Features |
|
| R1-2004967 |
LS on updated Rel-16 RAN1 UE features lists for LTE |
RAN1, NTT DOCOMO, AT&T |
| R1-2004968 |
RAN1 UE features list for Rel-16 LTE after RAN1#101-e |
Moderators (AT&T, NTT DOCOMO) |
| R1-2005118 |
LS on further updated Rel-16 RAN1 UE features list for LTE |
RAN1, NTT DOCOMO, AT&T |
| R1-2005119 |
Updated RAN1 UE features list for Rel-16 LTE after RAN1#101-e |
Moderators (AT&T, NTT DOCOMO, INC.) |
| 6.2.5.1 |
UE features for additional MTC enhancements |
|
| R1-2003787 |
UE features for eMTC |
Qualcomm Incorporated |
| R1-2003799 |
Discussion on UE features for additional MTC enhancements |
ZTE |
| R1-2004169 |
Rel-16 UE features for LTE-MTC |
Huawei, HiSilicon |
| R1-2004378 |
Summary on UE features for additional MTC enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2004661 |
On the RAN1 UE feature list for Rel-16 LTE-MTC |
Ericsson |
| R1-2004812 |
Summary on [101-e-LTE-UEFeatures-eMTC-01] |
Moderator (NTT DOCOMO, INC.) |
| 6.2.5.2 |
UE features for additional enhancements for NB-IoT |
|
| R1-2003788 |
UE features for NB-IoT |
Qualcomm Incorporated |
| R1-2003800 |
Discussion on UE features for additional enhancements for NB-IoT |
ZTE |
| R1-2004379 |
Summary on UE features for additional enhancements for NB-IoT |
Moderator (NTT DOCOMO, INC.) |
| R1-2004813 |
Summary on [101-e-LTE-UEFeatures-NBIoT-01] |
Moderator (NTT DOCOMO, INC.) |
| 6.2.5.3 |
UE features for DL MIMO efficiency enhancements for LTE |
|
| R1-2003467 |
UE features of DL MIMO efficiency enhancements for LTE |
ZTE |
| R1-2003789 |
UE features for MIMO |
Qualcomm Incorporated |
| R1-2003926 |
Remaining issue on RAN1 UE feature for LTE MIMO |
LG Electronics |
| R1-2004166 |
Rel-16 UE features for LTE MIMO |
Huawei, HiSilicon |
| R1-2004277 |
Summary of UE features for DL MIMO efficiency enhancements for LTE |
Moderator (AT&T) |
| R1-2004430 |
On UE features for LTE DL MIMO efficiency enhancements |
Ericsson |
| R1-2005024 |
Summary of Email Discussion/Approval [101-e-LTE-DL_MIMO_EE-UEFeatures-01] |
Moderator (AT&T) |
| 6.2.5.4 |
UE features for LTE-based 5G terrestrial broadcast |
|
| R1-2004278 |
Summary of UE features for LTE-based 5G terrestrial broadcast |
Moderator (AT&T) |
| 6.2.5.5 |
Other |
|
| R1-2003571 |
Discussion on Rel-16 LTE UE features for 5G V2X |
LG Electronics |
| R1-2004081 |
Disconssion on LTE feature list for 5G_V2X_NRSL |
OPPO |
| R1-2004279 |
Summary of Other UE features for LTE |
Moderator (AT&T) |
| R1-2004552 |
LTE UE features for V2X |
Ericsson |
| R1-2005112 |
Summary of email discussion/approval [101-e-Post-NR(LTE)-UE-Features-06] |
Moderator (AT&T) |
| 7.1 |
Maintenance of Release 15 NR |
|
| R1-2004676 |
RAN1#101-e preparation phase on NR Rel-15 CRs |
Ad-hoc Chair (Samsung) |
| R1-2004677 |
RAN1#101-e preparation phase output on NR Rel-15 CRs |
Ad-hoc Chair (Samsung) |
| R1-2005084 |
Session notes for 7.1 (Maintenance of Release 15 NR) |
Ad-hoc Chair (Samsung) |
| 7.1.1 |
Maintenance for Initial access and mobility |
|
| R1-2003704 |
Correction on RRC parameter of failureDetectionResources |
ZTE |
| R1-2004110 |
Discussion on the QCL assumption for paging reception |
OPPO |
| R1-2004111 |
Draft CR on the QCL assumption for paging reception |
OPPO |
| 7.1.2 |
Maintenance for MIMO |
|
| R1-2003357 |
Discussion on UL codebook subset |
vivo |
| R1-2003358 |
Draft CR on UL codebook subset |
vivo |
| R1-2003359 |
Discussion on CR on port and csi-rs resource occupation |
vivo |
| R1-2003360 |
Draft CR on port and csi-rs resource occupation |
vivo |
| R1-2003482 |
Draft CR on SRS for 38.214 |
ZTE |
| R1-2003591 |
Discussion on QCL assumption for PDSCH DM-RS |
CATT |
| R1-2004205 |
Correction to contention-based beam failure recovery |
Ericsson |
| R1-2004206 |
Clarifications on TRS configuration with duplexing direction change |
Apple |
| R1-2004207 |
Discussion on applicable time for PDSCH and PUSCH beam indication |
Apple |
| R1-2004208 |
Clarification on UE capability within a slot across serving cells |
Apple |
| R1-2004209 |
Draft CR on applicable time for PDSCH beam indication |
Apple |
| R1-2004210 |
Draft CR on applicable time for PUSCH beam indication |
Apple |
| R1-2004211 |
Draft CR on QCL assumption for DL PT-RS and DMRS |
Apple |
| R1-2004212 |
Draft CR on QCL indication for CSI-RS |
Apple |
| R1-2004260 |
PUCCH Spatial Relation after CBRA BFR |
Nokia, Nokia Shanghai Bell |
| R1-2004261 |
Clarification on the number of occupied CPUs and delay requirements for CSI reports using PUSCH |
Nokia, Nokia Shanghai Bell |
| R1-2004262 |
Clarification on which UE capability component indicates the number of supported simultaneous CSI calculations N_CPU |
Nokia, Nokia Shanghai Bell |
| R1-2004263 |
Correction of RRC parameter name for AP-TRS |
Nokia, Nokia Shanghai Bell |
| R1-2004429 |
Clarification on sp-CSI-RS capability |
Ericsson |
| R1-2004435 |
Draft CR on CSI report based on inactive resources |
Qualcomm Incorporated |
| R1-2004436 |
Discussion paper on CSI report based on inactive resources |
Qualcomm Incorporated |
| R1-2004437 |
draft CR on BWP for CORESET 0 beam reset by RACH |
Qualcomm Incorporated |
| R1-2004438 |
draft CR on L1-RSRP EPRE |
Qualcomm Incorporated |
| R1-2004439 |
draft CR on stop monitoring explicit BFD RS after BFR response |
Qualcomm Incorporated |
| R1-2004766 |
CR on SRS for 38.214 |
ZTE |
| R1-2004767 |
CR on SRS for 38.214 |
ZTE |
| R1-2004869 |
CR on port and csi-rs resource counting |
vivo |
| R1-2004870 |
CR on port and csi-rs resource counting |
vivo |
| R1-2004910 |
Correction of RRC parameter name for AP-TRS |
Nokia, Nokia Shanghai Bell |
| 7.1.3 |
Maintenance for Scheduling/HARQ aspects |
|
| R1-2003361 |
Clarification on UE behavior with empty list for SFI combination per cell |
vivo |
| R1-2003362 |
Draft CR on 38.214 rate-matching for PDSCH with SPS |
vivo |
| R1-2003363 |
Disucssion on PUSCH skipping with overlapping UCI on PUCCH |
vivo |
| R1-2003364 |
Correction on PUSCH skipping with overlapping UCI on PUCCH |
vivo |
| R1-2003592 |
Correction on the definition for timeline condition |
CATT |
| R1-2003593 |
Correction for PUCCH repetition transmission |
CATT |
| R1-2003594 |
Clarification on PUSCH frequency hopping |
CATT |
| R1-2003595 |
Correction for SP-CSI reporting on PUSCH |
CATT |
| R1-2003596 |
Correction for UCI on PUSCH without UL-SCH |
CATT |
| R1-2003597 |
Correction for SPS HARQ-ACK feedback in type2 HARQ-ACK codebook |
CATT |
| R1-2003705 |
Clarification on dynamic PUSCH skipping with overlapping CSI HARQ-ACK on PUCCH |
ZTE |
| R1-2004121 |
Correction on out-of-order HARQ of SPS PDSCH release |
OPPO |
| R1-2004308 |
UL grant overridden between configured grant and RAR grant |
ASUSTeK |
| R1-2004316 |
Correction on RAR grant overriding configured grant |
ASUSTeK |
| R1-2004319 |
PUCCH slot for PUCCH repetition |
ASUSTeK |
| R1-2004321 |
Correction on rate matching output sequence length |
Sharp |
| R1-2004375 |
CR on UCI bit sequence determination |
ASUSTeK |
| R1-2004380 |
CR on PUCCH group clarification |
NTT DOCOMO, INC. |
| R1-2004537 |
PUSCH slot-aggregation and A-CSI multiplexing |
Ericsson |
| R1-2004573 |
CR on multi-slot PUCCH repetition overlap with a single PUSCH |
ASUSTeK |
| R1-2004614 |
Clarification on UCI multiplexing on PUSCH |
Huawei, HiSilicon |
| R1-2004615 |
Corrections on multiplexing UCI from multiple PUCCHs on PUSCH |
Huawei, HiSilicon |
| R1-2004616 |
Corrections on dynamic PUSCH skipping with overlapping with PUCCH |
Huawei, HiSilicon |
| R1-2004617 |
Corrections on dynamic PUSCH skipping without overlapping with PUCCH |
Huawei, HiSilicon |
| R1-2004622 |
Clarification on symbol direction for the CORESET of Type0-PDCCH CSS set |
Huawei, HiSilicon |
| R1-2004623 |
Correction on symbol direction for the CORESET of Type0-PDCCH CSS set |
Huawei, HiSilicon |
| R1-2004630 |
Clarification on description of supported components of PDSCH ratematching capabilities in TS 38.306 |
Huawei, HiSilicon |
| R1-2004768 |
CR on 38.214 rate-matching for PDSCH with SPS |
vivo |
| R1-2004769 |
CR on 38.214 rate-matching for PDSCH with SPS |
vivo |
| R1-2004855 |
Correction for SP-CSI reporting on PUSCH |
CATT |
| R1-2004856 |
Correction for SP-CSI reporting on PUSCH |
CATT |
| R1-2005044 |
Correction on 38.214 for PUSCH with UL skipping |
vivo |
| 7.1.4 |
Maintenance for NR-LTE co-existence |
|
| R1-2003706 |
Correction on NE-DC power sharing |
ZTE |
| 7.1.5 |
Maintenance for UL power control |
|
| R1-2003598 |
Correction on SRS power control |
CATT |
| R1-2003599 |
Correction on SRS power control |
CATT |
| R1-2004158 |
Correction on PUSCH with a Type 1 configured grant |
Huawei, HiSilicon |
| 7.1.6 |
Other |
|
| R1-2004589 |
Correction for inconsistent shadow fading parameters in NTN rural scenario |
Nokia, Nokia Shanghai Bell |
| R1-2004590 |
Correction for inconsistent shadow fading parameters in NTN rural scenario |
Nokia, Nokia Shanghai Bell |
| R1-2004750 |
Correction for inconsistent shadow fading parameters in NTN rural scenario |
Nokia, Nokia Shanghai Bell |
| R1-2004841 |
LS on inconsistent shadow fading parameters in NTN rural scenario in TR 38.811 |
RAN1, Nokia |
| 7.2 |
Maintenance of Release 16 NR |
|
| R1-2003854 |
Rel-16 proposals for editors’ alignment CRs |
Samsung |
| R1-2004160 |
Discussion on Inter-RAT measurement to support SRVCC |
Huawei, HiSilicon, Lenovo, Motorola Mobility, China Unicom |
| R1-2004634 |
Draft 38.212 CR RRC IE name fix to dynamic frequency domain resource allocation type selection (Rel-15 origin) |
Nokia, Nokia Shanghai Bell |
| R1-2004635 |
Draft 38.214 CR Corrections to PDSCH PRB bundling notation (Rel-15 origin) |
Nokia, Nokia Shanghai Bell |
| R1-2004636 |
Correction to TBS determination when 3824
| Nokia, Nokia Shanghai Bell |
|
| R1-2004637 |
Introduction of UE UTRAN FDD measurements for SRVCC from NR to UMTS |
Nokia, Nokia Shanghai Bell |
| R1-2004857 |
Correction to TBS determination when 3824
| Nokia, Nokia Shanghai Bell |
|
| R1-2004862 |
Correction to TBS determination when 3824
| Nokia, Nokia Shanghai Bell |
|
| R1-2004905 |
Introduction of UE UTRAN FDD measurements for SRVCC from NR to UMTS |
Intel Corporation |
| R1-2005050 |
Updated consolidated parameter list for Rel-16 NR |
Moderator (Qualcomm) |
| R1-2005051 |
LS on updated Rel-16 NR parameter lists |
RAN1, Qualcomm |
| R1-2005122 |
Corrections to NR-based access to unlicensed spectrum |
Ericsson |
| R1-2005123 |
Corrections to NR positioning support |
Ericsson |
| R1-2005124 |
Corrections to MIMO enhancements |
Ericsson |
| R1-2005125 |
Corrections to two-step RACH |
Ericsson |
| R1-2005126 |
Corrections to cross-carrier scheduling with different numerologies |
Ericsson |
| R1-2005127 |
Corrections to V2X |
Ericsson |
| R1-2005128 |
Corrections to integrated access and backhaul for NR |
Ericsson |
| R1-2005129 |
Additional corrections to NR-based access to unlicensed spectrum |
Ericsson |
| R1-2005130 |
Corrections to MIMO enhancements |
Qualcomm |
| R1-2005131 |
Corrections to NR V2X |
Qualcomm |
| R1-2005132 |
Corrections for power saving |
Huawei |
| R1-2005133 |
Corrections on 5G V2X sidelink features |
Huawei |
| R1-2005134 |
Corrections in TS 38.212 for NR postioning |
Huawei |
| R1-2005135 |
Miscelleanous corrections in TS 38.212 for NR MIMO |
Huawei |
| R1-2005136 |
Corrections for URLLC |
Huawei |
| R1-2005137 |
Corrections for Rel-16 NR-U |
Huawei |
| R1-2005138 |
Corrections for NR IAB |
Huawei |
| R1-2005139 |
Corrections on integrated access and backhaul |
Samsung |
| R1-2005140 |
Corrections on Ultra Reliable Low Latency Communications Enhancements |
Samsung |
| R1-2005141 |
Corrections on UE power savings |
Samsung |
| R1-2005142 |
Corrections on Sidelink |
Samsung |
| R1-2005143 |
Corrections on Positioning |
Samsung |
| R1-2005144 |
Corrections on shared spectrum channel access |
Samsung |
| R1-2005145 |
Corrections on MIMO enhancements |
Samsung |
| R1-2005146 |
Corrections on Industrial IoT |
Samsung |
| R1-2005147 |
Corrections on NR-DC and on Cross-carrier Scheduling with Different Numerologies |
Samsung |
| R1-2005148 |
Corrections on two-step RACH |
Samsung |
| R1-2005149 |
Introduction of UL transmission switching |
Samsung |
| R1-2005150 |
Corrections on Mobility Enhancements |
Samsung |
| R1-2005151 |
Corrections on half-duplex operation in CA with unpaired spectrum |
Samsung |
| R1-2005152 |
Corrections of cross-slot scheduling restriction |
Nokia, Nokia Shanghai Bell |
| R1-2005153 |
Correction of two-step RACH |
Nokia, Nokia Shanghai Bell |
| R1-2005154 |
Corrections on NR URLLC support |
Nokia, Nokia Shanghai Bell |
| R1-2005155 |
Corrections on Industrial IoT |
Nokia, Nokia Shanghai Bell |
| R1-2005156 |
Corrections of NR positioning support |
Nokia, Nokia Shanghai Bell |
| R1-2005157 |
Corrections on NR - U |
Nokia, Nokia Shanghai Bell |
| R1-2005158 |
Corrections on NR V2X |
Nokia, Nokia Shanghai Bell |
| R1-2005159 |
Corrections on Cross-carrier Scheduling with Different Numerologies |
Nokia, Nokia Shanghai Bell |
| R1-2005160 |
Corrections on NR enhanced MIMO |
Nokia, Nokia Shanghai Bell |
| R1-2005161 |
Correction on SRS-RSRP reception procedure for CLI |
Nokia, Nokia Shanghai Bell |
| R1-2005162 |
TEI16: Correction on aperiodic CSI-RS triggering with beam switching timing of 224 and 336 and on CSI reporting |
Nokia, Nokia Shanghai Bell |
| R1-2005163 |
Correction to TBS determination when 3824
| Nokia, Nokia Shanghai Bell |
|
| R1-2005164 |
Editorial corrections |
Nokia, Nokia Shanghai Bell |
| R1-2005165 |
Corrections to V2X measurement definitions |
Intel Corporation |
| R1-2005166 |
Correction to UL Relative Time of Arrival definition |
Intel Corporation |
| R1-2005167 |
Corrections to intra/inter-frequency measurement for NR positioning |
Intel Corporation |
| R1-2005182 |
Corrections to single Tx switched uplink solution for EN-DC feature of Rel-16 MR DC/CA |
Motorola Mobility |
| 7.2.1.1 |
Channel Structure for Two-Step RACH |
|
| R1-2003365 |
Remaining issues on channel structure for 2-step RACH |
vivo |
| R1-2003455 |
Remaining issues of the channel structure for 2-step RACH |
ZTE, Sanechips |
| R1-2003457 |
FL summary on the maintenance of the 2-step RACH channel strucutre |
Moderator (ZTE) |
| R1-2003503 |
Corrections on channel structure of 2-step RACH |
Huawei, HiSilicon |
| R1-2003600 |
Remaining issues on 2-step RACH channel structure |
CATT |
| R1-2003724 |
Remaining details of channel structure for 2-step RACH |
Intel Corporation |
| R1-2003855 |
Channel Structure for Two-Step RACH |
Samsung |
| R1-2003978 |
Remaining issues on channel structure for 2-step RACH |
Spreadtrum Communications |
| R1-2004099 |
Discussion on Channel Structure for Two-step RACH |
OPPO |
| R1-2004130 |
Remaining details of Channel Structure for 2-step RACH |
LG Electronics |
| R1-2004213 |
Remaining issues on channel structure for 2-step RACH |
Apple |
| R1-2004347 |
Channel Structure Related Corrections For 2-Step RACH |
Ericsson |
| R1-2004381 |
Maintenance for Channel Structure for Two-Step RACH |
NTT DOCOMO, INC. |
| R1-2004440 |
Remaining issues and clarification on channel structure for Two-Step RACH |
Qualcomm Incorporated |
| R1-2004588 |
Discussion on remaining issues related to channel structure for Two-step RACH |
Nokia, Nokia Shanghai Bell |
| R1-2004833 |
Summary of email discussion [101-e-NR-2step-RACH-01] |
Moderator (ZTE) |
| R1-2004834 |
Summary of email discussion [101-e-NR-2step-RACH-02] |
Moderator (ZTE) |
| R1-2004835 |
Summary of email discussion [101-e-NR-2step-RACH-03] |
Moderator (ZTE) |
| 7.2.1.2 |
Procedure for Two-step RACH |
|
| R1-2003366 |
Remaining issues on procedure for 2-step RACH |
vivo |
| R1-2003456 |
Remaining issues of the 2-step RACH procedures |
ZTE, Sanechips |
| R1-2003458 |
FL summary on the maintenance of the 2-step RACH procedures |
Moderator (ZTE) |
| R1-2003504 |
Corrections on procedure of 2-step RACH |
Huawei, HiSilicon |
| R1-2003601 |
Remaining issues on 2-step RACH procedure |
CATT |
| R1-2003725 |
Remaining details of procedure for 2-step RACH |
Intel Corporation |
| R1-2003856 |
Procedure for Two-step RACH |
Samsung |
| R1-2003947 |
Remaining issue on 2-step RA procedure triggered by BFR |
CMCC |
| R1-2004100 |
Remaining issues for procedure of 2-step RACH |
OPPO |
| R1-2004131 |
Remaining details of Procedure for 2-step RACH |
LG Electronics |
| R1-2004348 |
Procedure Related Corrections for 2-Step RACH |
Ericsson |
| R1-2004382 |
Maintenance for Procedure for Two-step RACH |
NTT DOCOMO, INC. |
| R1-2004836 |
Summary of email discussion [101-e-NR-2step-RACH-04] |
Moderator (ZTE) |
| R1-2004966 |
Text proposals on the RAR terminology |
Moderator (ZTE) |
| 7.2.1.3 |
Other |
|
| R1-2004132 |
Remaining details of designing 2-step RACH for NR-U |
LG Electronics |
| R1-2004349 |
Remaining Issues for MsgA PUSCH Transmission in CFRA |
Ericsson |
| 7.2.2 |
Maintenance of NR-based Access to Unlicensed Spectrum |
|
| R1-2005090 |
Session notes for 7.2.2 (Maintenance of NR-based Access to Unlicensed Spectrum) |
Ad-Hoc Chair (Ericsson) |
| 7.2.2.1.1 |
Initial access signals/channels |
|
| R1-2003367 |
Remaining issues on initial access signals and channles |
vivo |
| R1-2003447 |
Remaining issues on the initial access signals for NR-U |
ZTE, Sanechips |
| R1-2003509 |
Maintenance on the initial access signals and channels |
Huawei, HiSilicon |
| R1-2003839 |
Initial access signals and channels |
Ericsson |
| R1-2003857 |
Initial access signals and channels for NR-U |
Samsung |
| R1-2004000 |
Remaining issues on initial access signals |
Spreadtrum Communications |
| R1-2004010 |
Remaining issues of initial access signals and channels for NR-U |
LG Electronics |
| R1-2004082 |
Discussion on the remaining issues of initial access signal/channel |
OPPO |
| R1-2004254 |
Remaining issues on Initial Access Signals and Channels for NR-U |
Nokia, Nokia Shanghai Bell |
| R1-2004752 |
FL summary for Initial signals and channels for NR-U |
Moderator (Qualcomm) |
| 7.2.2.1.2 |
DL signals and channels |
|
| R1-2003368 |
Remaining issues on physical DL channel design in unlicensed spectrum |
vivo |
| R1-2003448 |
Remaining issues on the DL channels for NR-U |
ZTE, Sanechips |
| R1-2003510 |
Maintenance on DL signals and channels |
Huawei, HiSilicon |
| R1-2003654 |
Remaining issues on DL signals and channels for NR-U |
MediaTek Inc. |
| R1-2003726 |
DL signals and channels for NR-unlicensed |
Intel Corporation |
| R1-2003840 |
DL signals and channels |
Ericsson |
| R1-2003858 |
DL signals and channels for NR-U |
Samsung |
| R1-2004002 |
Remaining issues in DL signals and channels for NR-U |
Spreadtrum Communications |
| R1-2004011 |
Remaining issues of DL signals and channels for NR-U |
LG Electronics |
| R1-2004083 |
Discussion on the remaining issues of DL signals and channels |
OPPO |
| R1-2004214 |
Remaining issues of DL signals and channels |
Apple |
| R1-2004255 |
Remaining issues on DL signals and channels |
Nokia, Nokia Shanghai Bell |
| R1-2004322 |
Remaining issues and corrections on DL signals and channels for NR-U |
Sharp |
| R1-2004441 |
TP for DL signals and channels for NR-U |
Qualcomm Incorporated |
| R1-2004503 |
Feature lead summary for NR-U DL Signals and Channels |
Moderator (Lenovo) |
| R1-2004516 |
Maintenance for DL signals and channels for NR-U |
Panasonic |
| R1-2004528 |
Text proposal for search space group switching |
Google Inc. |
| R1-2004851 |
Summary of email discussion [101-e-NR-unlic-NRU-DL_Signals_and_Channels-01] on Search Space |
Moderator (Lenovo) |
| R1-2004852 |
Summary of email discussion [101-e-NR-unlic-NRU-DL_Signals_and_Channels-02] on DCI format 2_0 indications |
Moderator (Lenovo) |
| R1-2004853 |
Summary of email discussion [101-e-NR-unlic-NRU-DL_Signals_and_Channels-03] on CSI-RS and related aspects |
Moderator (Lenovo) |
| R1-2004854 |
Summary of email discussion [101-e-NR-unlic-NRU-DL_Signals_and_Channels-04] on capturing prior agreements |
Moderator (Lenovo) |
| R1-2005011 |
Summary#2 of email discussion [101-e-NR-unlic-NRU-DL_Signals_and_Channels-01] on Search Space |
Moderator (Lenovo) |
| R1-2005012 |
Summary#2 of email discussion [101-e-NR-unlic-NRU-DL_Signals_and_Channels-02] on DCI format 2_0 indications |
Moderator (Lenovo) |
| R1-2005013 |
Summary#2 of email discussion [101-e-NR-unlic-NRU-DL_Signals_and_Channels-03] on CSI-RS and related aspects |
Moderator (Lenovo) |
| R1-2005014 |
Summary#2 of email discussion [101-e-NR-unlic-NRU-DL_Signals_and_Channels-04] on capturing prior agreements |
Moderator (Lenovo) |
| 7.2.2.1.3 |
UL signals and channels |
|
| R1-2003369 |
Remaining issues on physical UL channel design in unlicensed spectrum |
vivo |
| R1-2003449 |
Remaining issues on the UL channels for NR-U |
ZTE, Sanechips |
| R1-2003511 |
Maintenance on uplink signals and channels |
Huawei, HiSilicon |
| R1-2003655 |
Remaining issues on UL signals and channels for NR-U |
MediaTek Inc. |
| R1-2003727 |
UL signals and channels for NR-unlicensed |
Intel Corporation |
| R1-2003822 |
Text proposals for UL signals and channels for NR-U |
Lenovo, Motorola Mobility |
| R1-2003841 |
UL signals and channels |
Ericsson |
| R1-2003842 |
Feature Lead Summary for UL Signals and Channels |
Ericsson |
| R1-2003859 |
UL signals and channels for NR-U |
Samsung |
| R1-2004003 |
Remaining issues in UL signals and channels for NR-U |
Spreadtrum Communications |
| R1-2004012 |
Remaining issues of UL signals and channels for NR-U |
LG Electronics |
| R1-2004041 |
Remaining issues on UL signals and channels for NR-U |
Fujitsu |
| R1-2004084 |
Discussion on the remaining issues of UL signals and channels |
OPPO |
| R1-2004274 |
Remaining Issues on UL Signals and Channels for NR-U |
Nokia, Nokia Shanghai Bell |
| R1-2004323 |
Remaining issues on UL signals/channels for NR-U |
Sharp |
| R1-2004442 |
TP for UL signals and channels for NR-U |
Qualcomm Incorporated |
| R1-2004883 |
FL Summary for [101-e-NR-unlic-NRU-ULSignalsChannels-01] Email discussion/approval |
Moderator (Ericsson) |
| R1-2004884 |
FL Summary for [101-e-NR-unlic-NRU-ULSignalsChannels-02] Email discussion/approval |
Moderator (Ericsson) |
| R1-2004996 |
FL Summary#2 for [101-e-NR-unlic-NRU-ULSignalsChannels-01] Email discussion/approval |
Moderator (Ericsson) |
| R1-2004997 |
FL Summary#2 for [101-e-NR-unlic-NRU-ULSignalsChannels-02] Email discussion/approval |
Moderator (Ericsson) |
| R1-2004998 |
[Draft] LS to RAN2 on initial BWP for NR-U |
Ericsson |
| R1-2005016 |
LS to RAN2 on initial BWP for NR-U |
RAN1, Ericsson |
| 7.2.2.2.1 |
Channel access procedures |
|
| R1-2003370 |
Remaining issues on the channel access procedures |
vivo |
| R1-2003450 |
Remaining issues on the channel access procedure for NR-U |
ZTE, Sanechips |
| R1-2003512 |
Maintenance on the channel access procedure |
Huawei, HiSilicon |
| R1-2003656 |
Remaining issues on channel access for NR-U operation |
MediaTek Inc. |
| R1-2003728 |
Channel access mechanism for NR-unlicensed |
Intel Corporation |
| R1-2003843 |
Channel access procedures |
Ericsson |
| R1-2003860 |
Channel access procedures for NR-U |
Samsung |
| R1-2003972 |
Remaining issues on channel access procedures for NR-U |
ETRI |
| R1-2004013 |
Remaining issues of channel access procedure for NR-U |
LG Electronics |
| R1-2004085 |
Discussion on the remaining issues of channel access procedure |
OPPO |
| R1-2004182 |
Remaining issues on channel access procedures for NR-U |
Sony |
| R1-2004275 |
Remaining Issues on Channel Access Procedures for NR-U |
Nokia, Nokia Shanghai Bell |
| R1-2004443 |
TP for Channel access procedures for NR unlicensed |
Qualcomm Incorporated |
| R1-2004521 |
Remaining issues on channel access procedure for NR-U |
WILUS Inc. |
| R1-2004539 |
Feature lead summary on NR-U channel access procedures |
Moderator (Nokia) |
| R1-2004858 |
Feature lead summary#1 on email discussion [101-e-NR-unlic-NRU-ChAcc-01] |
Moderator (Nokia) |
| R1-2004859 |
Feature lead summary#1 on email discussion [101-e-NR-unlic-NRU-ChAcc-02] |
Moderator (Nokia) |
| R1-2004995 |
Feature lead summary#2 on email discussion [101-e-NR-unlic-NRU-ChAcc-01] |
Moderator (Nokia) |
| 7.2.2.2.2 |
Enhancements to initial access procedure |
|
| R1-2003306 |
FL summary for initial access procedure enhancements |
Moderator (Charter Communications, Inc) |
| R1-2003371 |
Remaining issues on initial access procedure for NR-U |
vivo |
| R1-2003451 |
Remaining issues on the initial access procedure for NR-U |
ZTE, Sanechips |
| R1-2003513 |
Maintenance on the initial access procedures |
Huawei, HiSilicon |
| R1-2003657 |
Remaining issues on initial access procedure for NR-U operation |
MediaTek Inc. |
| R1-2003729 |
Enhancements to initial access and mobility for NR-unlicensed |
Intel Corporation |
| R1-2003844 |
Enhancements to initial access procedures |
Ericsson |
| R1-2003861 |
Initial access procedures for NR-U |
Samsung |
| R1-2003973 |
Remaining issues on initial access procedure for NR-U |
ETRI |
| R1-2004001 |
Remaining issues on initial access procedure |
Spreadtrum Communications |
| R1-2004014 |
Remaining issues of initial access and mobility for NR-U |
LG Electronics |
| R1-2004086 |
Discussion on the remaining issues of enhancements to initial access procedure |
OPPO |
| R1-2004444 |
TP for Initial access and mobility procedures for NR-U |
Qualcomm Incorporated |
| R1-2004526 |
On Enhancements to Initial Access Procedure for NR-U |
Nokia, Nokia Shanghai Bell |
| R1-2004775 |
Outcome of email thread [101-e-NR-unlic-NRU-InitAccessProc-01] |
Moderator (Charter Communications) |
| R1-2004776 |
Outcome of email thread [101-e-NR-unlic-NRU-InitAccessProc-02] |
Moderator (Charter Communications) |
| R1-2004777 |
Outcome of email thread [101-e-NR-unlic-NRU-InitAccessProc-03] |
Moderator (Charter Communications) |
| R1-2004778 |
Outcome of email thread [101-e-NR-unlic-NRU-InitAccessProc-04] |
Moderator (Charter Communications) |
| R1-2004873 |
Summary of [101-e-NR-unlic-NRU-InitAccessProc-06] |
Moderator (Huawei) |
| R1-2004885 |
FL Summary for [101-e-NR-unlic-NRU-InitAccessProc-05] Email discussion/approval |
Moderator (Ericsson) |
| R1-2004903 |
[DRAFT] Reply LS on transmit power of CSI-RS across different occasions |
Huawei |
| R1-2004911 |
FL Summary for [101-e-NR-unlic-NRU-InitAccessProc-07] Email discussion/approval |
Moderaror (Nokia) |
| R1-2004913 |
Outcome#2 of email thread [101-e-NR-unlic-NRU-InitAccessProc-04] |
Moderator (Charter Communications) |
| R1-2004914 |
[Draft] LS to RAN2 on NR-U RSSI Measurement Duration |
Charter Communications |
| R1-2004915 |
LS to RAN2 on NR-U RSSI Measurement Duration |
RAN1, Charter Communications |
| R1-2004949 |
Reply LS on transmit power of CSI-RS across different occasions |
RAN1, Huawei |
| R1-2004992 |
Reply LS on NR-U SSB monitoring capabilities |
RAN1, Nokia |
| R1-2005015 |
Outcome#2 of email thread [101-e-NR-unlic-NRU-InitAccessProc-01] |
Moderator (Charter Communications) |
| 7.2.2.2.3 |
HARQ enhancement |
|
| R1-2003372 |
Remaining issues on HARQ operation for NR-U |
vivo |
| R1-2003452 |
Remaining issues on the HARQ for NR-U |
ZTE, Sanechips |
| R1-2003514 |
Maintenance on HARQ-ACK enhancement |
Huawei, HiSilicon |
| R1-2003658 |
Remaining issues on HARQ operation for NR-U |
MediaTek Inc. |
| R1-2003730 |
Enhancements to HARQ for NR-unlicensed |
Intel Corporation |
| R1-2003823 |
Text proposals for HARQ enhancement for NR-U |
Lenovo, Motorola Mobility |
| R1-2003845 |
HARQ enhancement |
Ericsson |
| R1-2003862 |
HARQ enhancement for NR-U |
Samsung |
| R1-2004015 |
Remaining issues of HARQ procedure for NR-U |
LG Electronics |
| R1-2004087 |
Discussion on the remaining issues of HARQ enhancements |
OPPO |
| R1-2004257 |
Remaining issues on NR-U HARQ scheduling and feedback |
Nokia, Nokia Shanghai Bell |
| R1-2004325 |
Remaining issues and corrections on HARQ enhancement for NR-U |
Sharp |
| R1-2004445 |
TP for Enhancements to Scheduling and HARQ Operation for NR-U |
Qualcomm Incorporated |
| R1-2004529 |
Text proposal for enhanced dynamic HARQ procedures |
Google Inc. |
| R1-2004692 |
Feature lead summary#1 on NR-U HARQ |
Moderator (Huawei) |
| R1-2004744 |
Feature lead summary on 101-e-NR-unlic-NRU-HARQ-01 (enhanced Type-2 HARQ-ACK codebook) |
Moderator (Huawei) |
| R1-2004745 |
Feature lead summary on 101-e-NR-unlic-NRU-HARQ-02 (Type-3 HARQ-ACK codebook) |
Moderator (Huawei) |
| R1-2004746 |
Feature lead summary on 101-e-NR-unlic-NRU-HARQ-03 (NNK1 value) |
Moderator (Huawei) |
| R1-2004963 |
Feature lead summary#2 on 101-e-NR-unlic-NRU-HARQ-02 (Type-3 HARQ-ACK codebook) |
Moderator (Huawei) |
| R1-2004964 |
Feature lead summary#2 on 101-e-NR-unlic-NRU-HARQ-03 (NNK1 value) |
Moderator (Huawei) |
| 7.2.2.2.4 |
Configured grant enhancement |
|
| R1-2003373 |
Remaining issues on the enhancements to configured grant |
vivo |
| R1-2003375 |
Feature lead summary on NRU configured grant enhancement |
Moderator (vivo) |
| R1-2003453 |
Remaining issues on the configured grant for NR-U |
ZTE, Sanechips |
| R1-2003515 |
Maintenance on the configured grant procedures |
Huawei, HiSilicon |
| R1-2003731 |
Enhancements to configured grants for NR-unlicensed |
Intel Corporation |
| R1-2003824 |
Text proposals for configured grant enhancement for NR-U |
Lenovo, Motorola Mobility |
| R1-2003846 |
Configured grant enhancement |
Ericsson |
| R1-2003863 |
Configured grant enhancement for NR-U |
Samsung |
| R1-2004016 |
Remaining issues of configured grant for NR-U |
LG Electronics |
| R1-2004088 |
Discussion on the remaining issues of configured grant enhancements |
OPPO |
| R1-2004446 |
TP for Enhancements to configured grants for NR-U |
Qualcomm Incorporated |
| R1-2004575 |
Remaining Issues on Configured Grants for NR-U |
Nokia, Nokia Shanghai Bell |
| R1-2004707 |
Summary of prep email discussion on NRU-CG |
Moderator (vivo) |
| R1-2004796 |
Feature lead summary on [101-e-NR-unlic-NRU-CG-01] |
Moderator (vivo) |
| R1-2004984 |
Feature lead summary#2 on [101-e-NR-unlic-NRU-CG-01] |
Moderator (vivo) |
| R1-2005002 |
Feature lead summary#3 on [101-e-NR-unlic-NRU-CG-01] |
Moderator (vivo) |
| R1-2005073 |
Outcome of [101-e-NR-unlic-NRU-CG-01] |
Moderator (vivo) |
| 7.2.2.2.5 |
Wide-band operation |
|
| R1-2003374 |
Remaining issues on wideband operation in NR-U |
vivo |
| R1-2003454 |
Remaining issues on the wideband operation for NR-U |
ZTE, Sanechips |
| R1-2003516 |
Maintenance on the wideband operation procedures |
Huawei, HiSilicon |
| R1-2003659 |
Remaining issues on wideband operation for NR-U |
MediaTek Inc. |
| R1-2003847 |
Wideband operation |
Ericsson |
| R1-2003864 |
Wide-band operation for NR-U |
Samsung |
| R1-2004017 |
Remaining issues of wide-band operation for NR-U |
LG Electronics |
| R1-2004018 |
Summary on maintenance of wide-band operation for NR-U |
Moderator (LG Electronics) |
| R1-2004089 |
Discussion on the remaining issues of wide-band operations |
OPPO |
| R1-2004256 |
Remaining issues on Wideband operation in NR-U |
Nokia, Nokia Shanghai Bell |
| R1-2004324 |
Remaining issues on wideband operation for NR-U |
Sharp |
| R1-2004447 |
TP for Wideband operation for NR-U operation |
Qualcomm Incorporated |
| R1-2004511 |
Remaining issues on Rel-16 NR-U wideband operations |
Panasonic |
| R1-2004702 |
Summary#2 on maintenance of wide-band operation for NR-U |
Moderator (LG Electronics) |
| R1-2004737 |
Summary of email discussion [101-e-NR-unlic-NRU-WB-01] on DL/UL cell without intra-cell guard bands |
Moderator (LG Electronics) |
| R1-2004738 |
Summary of email discussion [101-e-NR-unlic-NRU-WB-02] on RB set and CORESET configuration |
Moderator (LG Electronics) |
| R1-2004904 |
Summary#2 of email discussion [101-e-NR-unlic-NRU-WB-01] on DL/UL cell without intra-cell guard bands |
Moderator (LG Electronics) |
| R1-2004983 |
Text proposal as outcome of email discussions [101-e-NR-unlic-NRU-WB-01] and [101-e-NR-unlic-NRU-WB-02] |
Moderator (LG Electronics) |
| 7.2.2.3 |
Other |
|
| R1-2003517 |
Other Maintenance for NR-U |
Huawei, HiSilicon |
| R1-2004090 |
Discussion on the other remaining issues |
OPPO |
| 7.2.3 |
Maintenance of Integrated Access and Backhaul for NR |
|
| R1-2004448 |
Proposed IAB updates to 38.300 |
Qualcomm Incorporated |
| R1-2004871 |
FL summary for [101-e-NR-IAB-05] - Updates to TS38.300 |
Moderator (Qualcomm Incorporated) |
| R1-2004872 |
LS on IAB updates to 38.300 |
RAN1, Qualcomm |
| R1-2005085 |
Session notes for 7.2.3 (Maintenance of Integrated Access and Backhaul for NR) |
Ad-hoc Chair (Samsung) |
| 7.2.3.3 |
Mechanisms for resource multiplexing among backhaul and access links |
|
| R1-2003376 |
Remaining aspects for resource multiplexing among backhaul and access links |
vivo |
| R1-2003505 |
Remaining issues on resource multiplexing among backhaul and access links |
Huawei, HiSilicon |
| R1-2003544 |
Remaining issues in IAB resource multiplexing |
ZTE, Sanechips |
| R1-2003732 |
Discussion on soft resource availability indication |
Intel Corporation |
| R1-2003948 |
Remaining issues on mechanisms for resource multiplexing among backhaul and access links |
CMCC |
| R1-2003974 |
Discussion on IAB resource multiplexing |
ETRI |
| R1-2004133 |
Remainig details on IAB resource multiplexing |
LG Electronics |
| R1-2004280 |
Remaining maintenance issues for IAB resource multiplexing |
AT&T |
| R1-2004281 |
Summary of Mechanisms for resource multiplexing among backhaul and access links |
Moderator (AT&T) |
| R1-2004449 |
Remaining issues on IAB resource management |
Qualcomm Incorporated |
| R1-2004582 |
Mechanisms for resource multiplexing among backhaul and access links |
Ericsson |
| R1-2004759 |
[Draft] Reply LS on cell specific signal/channel configurations |
ZTE |
| R1-2004760 |
Reply LS on cell specific signal/channel configurations |
RAN1, ZTE |
| R1-2004784 |
LS response to RAN2 LS on Guard Symbols in IAB |
RAN1, Samsung |
| 7.2.3.4 |
Mechanism to support the "case-1" OTA timing alignment |
|
| R1-2004583 |
Mechanism to support the “case-1” OTA timing alignment |
Ericsson |
| R1-2004666 |
FL summary #1 on IAB case-1 timing |
Moderator (ZTE) |
| 7.2.3.5 |
Other |
|
| R1-2004584 |
On RAN4 UE features for IAB-MTs |
Ericsson |
| 7.2.4 |
Maintenance for 5G V2X with NR sidelink |
|
| R1-2003698 |
TR 37.985, “Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR”, v1.3.0 |
Huawei |
| R1-2004764 |
TR 37.985, “Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR”, v1.3.0 |
Huawei |
| R1-2004861 |
TR 37.985, “Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR”, v1.4.0 |
Huawei |
| R1-2005121 |
Draft v2.0.0 of TR 37.985, “Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR” |
Huawei |
| 7.2.4.1 |
Physical layer structure for sidelink |
|
| R1-2003308 |
Remaining details of Physical layer structure for sidelink |
Nokia, Nokia Shanghai Bell |
| R1-2003377 |
Remaining issues on physical layer structure for NR sidelink |
vivo |
| R1-2003493 |
Remaining details of sidelink physical layer structure |
Huawei, HiSilicon |
| R1-2003561 |
Discussion on physical layer structure for NR sidelink |
LG Electronics |
| R1-2003573 |
Remaining issues of NR sidelink physical layer structure |
ZTE, Sanechips |
| R1-2003611 |
Remaining issues on physical layer structure for NR sidelink |
CATT |
| R1-2003681 |
Discussion on sidelink physical layer structure |
MediaTek Inc. |
| R1-2003700 |
Remaining issues for NR V2X structure |
ASUSTeK |
| R1-2003713 |
Remaining Issues in Physical Layer Structures for NR V2X |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2003733 |
Remaining opens of L1 structure for NR V2X sidelink design |
Intel Corporation |
| R1-2003805 |
Remaining details on physical layer structure for the sidelink |
Futurewei |
| R1-2003825 |
Remaining issues on physical layer structure for NR sidelink |
Lenovo, Motorola Mobility |
| R1-2003870 |
Feature lead summary#1 for agenda item 7.2.4.1 Physical layer structure for sidelink |
Moderator (Samsung) |
| R1-2003871 |
Feature lead summary#2 for agenda item 7.2.4.1 Physical layer structure for sidelink |
Moderator (Samsung) |
| R1-2003872 |
On Physical Layer Structures for NR Sidelink |
Samsung |
| R1-2003941 |
Remaining issue on physical layer structure for sidelink in NR V2X |
Panasonic Corporation |
| R1-2003949 |
Remaining issues on physical layer structure for sidelink |
CMCC |
| R1-2003989 |
Remaining issues of physical layer structure for sidelink |
Spreadtrum Communications |
| R1-2004070 |
Draft text proposals on physical layer structure for NR-V2X |
OPPO |
| R1-2004170 |
Physical layer structure for sidelink |
TCL Communication Ltd. |
| R1-2004183 |
Remaining issues on physical layer structure for NR sidelink |
Sony |
| R1-2004215 |
Remaining Issues of Physical Layer Structure for NR V2X |
Apple |
| R1-2004293 |
Remaining Issues on Physical Layer Structure for NR V2X |
InterDigital, Inc. |
| R1-2004309 |
Remaining issues on physical layer structure |
NEC |
| R1-2004326 |
Remaining issues on physical layer structure for NR sidelink |
Sharp |
| R1-2004383 |
Remaining issues on sidelink physical layer structure |
NTT DOCOMO, INC. |
| R1-2004450 |
Considerations on Physical Layer aspects of NR V2X |
Qualcomm Incorporated |
| R1-2004530 |
Remain details on physical layer structure for NR V2X |
ITL |
| R1-2004542 |
Physical layer structure for NR sidelink |
Ericsson |
| R1-2004570 |
Remaining issues of V2X PHY layer structure |
Mitsubishi Electric RCE |
| R1-2004756 |
Considerations on Physical Layer aspects of NR V2X |
Qualcomm Incorporated |
| R1-2005018 |
Text Proposals from [101-e-NR-5G_V2X_NRSL-PHYstructure-01] |
Moderator (Samsung) |
| R1-2005019 |
Text Proposals from [101-e-NR-5G_V2X_NRSL-PHYstructure-02] |
Moderator (Samsung) |
| R1-2005020 |
Text Proposals from [101-e-NR-5G_V2X_NRSL-PHYstructure-03] |
Moderator (Samsung) |
| R1-2005021 |
Text Proposals from [101-e-NR-5G_V2X_NRSL-PHYstructure-04] |
Moderator (Samsung) |
| 7.2.4.2.1 |
Mode 1 |
|
| R1-2003309 |
Remaining details of Resource Allocation Mode 1 |
Nokia, Nokia Shanghai Bell |
| R1-2003378 |
Remaining issues on mode 1 resource allocation mechanism |
vivo |
| R1-2003494 |
Remaining details of sidelink resource allocation mode 1 |
Huawei, HiSilicon |
| R1-2003548 |
Remaining issues in Mode-1 |
ZTE, Sanechips |
| R1-2003562 |
Discussion on resource allocation for Mode 1 |
LG Electronics |
| R1-2003612 |
Remaining issues on Mode 1 resource allocation in NR V2X |
CATT |
| R1-2003670 |
Sidelink mode-1 resource allocation |
MediaTek Inc. |
| R1-2003714 |
Remaining Issues in Resource Allocation for Mode 1 NR V2X |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2003734 |
Remaining opens of Mode-1 NR V2X sidelink design |
Intel Corporation |
| R1-2003806 |
Remaining details on mode-1 resource allocation |
Futurewei |
| R1-2003826 |
Remaining issues on resource allocation for NR sidelink Mode 1 |
Lenovo, Motorola Mobility |
| R1-2003873 |
On Mode 1 for NR Sidelink |
Samsung |
| R1-2003950 |
Remaining issues on mode 1 resource allocation mechanism |
CMCC |
| R1-2003990 |
Remaining issues in NR sidelink mode 1 resource allocation |
Spreadtrum Communications |
| R1-2004042 |
Remaining issues on mode 1 resource allocation for NR V2X |
Fujitsu |
| R1-2004071 |
Remaining issues of mode 1 resource allocation for NR-V2X |
OPPO |
| R1-2004216 |
Remaining Issues of Mode 1 Resource Allocation |
Apple |
| R1-2004294 |
Remaining Issues on NR Sidelink Mode 1 Resource Allocation |
InterDigital, Inc. |
| R1-2004327 |
Remaining issues on resource allocation mode 1 for NR sidelink |
Sharp |
| R1-2004342 |
Mode-1 resource allocation for NR V2X |
ITL |
| R1-2004344 |
Remaining issues on sidelink resource allocation mode 1 |
ASUSTeK |
| R1-2004384 |
Remaining issues on resource allocation mechanism mode 1 |
NTT DOCOMO, INC. |
| R1-2004451 |
Sidelink Resource Allocation Mode 1 |
Qualcomm Incorporated |
| R1-2004543 |
Resource Allocation Mode 1 for NR SL |
Ericsson |
| R1-2004554 |
Feature lead summary#1 on Resource allocation for NR sidelink Mode 1 |
Moderator (Ericsson) |
| R1-2004555 |
Feature lead summary#2 on Resource allocation for NR sidelink Mode 1 |
Moderator (Ericsson) |
| R1-2004591 |
On Resource Allocation Mode 1 for NR V2X |
Convida Wireless |
| R1-2004881 |
[Draft] Reply on LS on RAN1 views on sidelink |
Ericsson |
| R1-2004921 |
Reply on LS on RAN1 views on sidelink |
RAN1, Ericsson |
| R1-2005006 |
TPs for 38.213 and TP 38.214 for the agreements in [101-e- NR-5G_V2X_NRSL-Mode-1-01] |
Moderator (Ericsson) |
| R1-2005007 |
TPs for 38.212, 38.213, and 38.214 for the agreements in [101-e- NR-5G_V2X_NRSL-Mode-1-02] |
Moderator (Ericsson) |
| R1-2005008 |
TPs for 38.212 and 38.213 for the agreements in [101-e- NR-5G_V2X_NRSL-Mode-1-03] |
Moderator (Ericsson) |
| 7.2.4.2.2 |
Mode 2 |
|
| R1-2003310 |
Remaining details of Resource Allocation Mode 2 |
Nokia, Nokia Shanghai Bell |
| R1-2003379 |
Remaining issues on mode 2 resource allocation mechanism |
vivo |
| R1-2003495 |
Remaining details of sidelink resource allocation mode 2 |
Huawei, HiSilicon |
| R1-2003549 |
Remaining issues in Mode-2 |
ZTE, Sanechips |
| R1-2003559 |
Remaining Issues on Sidelink Mode 2 Resource Allocation |
Panasonic Corporation |
| R1-2003563 |
Discussion on resource allocation for Mode 2 |
LG Electronics |
| R1-2003613 |
Remaining issues on Mode 2 resource allocation in NR V2X |
CATT |
| R1-2003653 |
Remaining Issues on Resource Allocation in NR Sidelink Mode 2 |
ITRI |
| R1-2003671 |
Sidelink mode-2 resource allocation |
MediaTek Inc. |
| R1-2003703 |
Remaining issues for Mode 2 resource allocation in NR V2X |
ASUSTeK |
| R1-2003735 |
Remaining details of Mode-2 NR V2X sidelink design |
Intel Corporation |
| R1-2003807 |
Remaining details on mode-2 resource allocation |
Futurewei |
| R1-2003874 |
On Mode 2 for NR Sidelink |
Samsung |
| R1-2003991 |
Remaining issues in NR sidelink mode 2 resource allocation |
Spreadtrum Communications |
| R1-2004043 |
Remaining details on mode 2 resource allocation for NR V2X |
Fujitsu |
| R1-2004074 |
Discussion on remaining open issue for mode 2 |
OPPO |
| R1-2004171 |
Resource allocation for NR sidelink Mode 2 |
TCL Communication Ltd. |
| R1-2004217 |
Remaining Issues of Mode 2 Resource Allocation |
Apple |
| R1-2004295 |
Remaining Issues on NR Sidelink Mode 2 Resource Allocation |
InterDigital, Inc. |
| R1-2004310 |
Remaining issues on resource allocation Mode 2 |
NEC |
| R1-2004328 |
Remaining issues on resource allocation mode 2 for NR sidelink |
Sharp |
| R1-2004385 |
Remaining issues on resource allocation mechanism mode 2 |
NTT DOCOMO, INC. |
| R1-2004452 |
Sidelink Resource Allocation Mode 2 |
Qualcomm Incorporated |
| R1-2004531 |
Remain details on mode-2 resource allocation for NR V2X |
ITL |
| R1-2004544 |
Resource allocation Mode 2 for NR SL |
Ericsson |
| R1-2004688 |
FL summary#1 of critical issues for 7.2.4.2.2 – V2X Mode 2 |
Moderator (Intel) |
| R1-2004715 |
FL summary#2 of critical issues for 7.2.4.2.2 – V2X Mode 2 |
Moderator (Intel) |
| R1-2004938 |
Outcome of [101-e-NR-5G_V2X_NRSL-Mode-2-01] |
Moderator (Intel) |
| R1-2004939 |
Outcome of [101-e-NR-5G_V2X_NRSL-Mode-2-02] |
Moderator (Intel) |
| R1-2004940 |
Outcome of [101-e-NR-5G_V2X_NRSL-Mode-2-03] |
Moderator (Intel) |
| R1-2004941 |
Outcome of [101-e-NR-5G_V2X_NRSL-Mode-2-04] |
Moderator (Intel) |
| R1-2004942 |
Outcome and TP of [101-e-NR-5G_V2X_NRSL-Mode-2-05] |
Moderator (Intel) |
| R1-2004943 |
TPs based on outcome of [101-e-NR-5G_V2X_NRSL-Mode-2-01] |
Moderator (Intel) |
| R1-2004944 |
TPs based on outcome of [101-e-NR-5G_V2X_NRSL-Mode-2-03] |
Moderator (Intel) |
| R1-2004945 |
TPs based on outcome of [101-e-NR-5G_V2X_NRSL-Mode-2-04] |
Moderator (Intel) |
| R1-2004946 |
[Draft] LS to RAN2 on resource allocation Mode-2 agreements related to QoS requirements |
Intel |
| R1-2004947 |
[Draft] LS to RAN2 on SL_RESOURCE_RESELECTION_COUNTER and period value provided to L1 |
Intel |
| R1-2005009 |
LS to RAN2 on resource allocation Mode-2 agreements related to QoS requirements |
RAN1, Intel |
| R1-2005010 |
LS to RAN2 on SL_RESOURCE_RESELECTION_COUNTER and period value provided to L1 |
RAN1, Intel |
| 7.2.4.2.3 |
Other |
|
| R1-2003380 |
Remaining issues for resource allocation |
vivo |
| R1-2003550 |
Prioritizations of remaining issues in Mode-1 and Mode-2 |
ZTE, Sanechips |
| R1-2004075 |
On other aspects of mode 2 resource allocation |
OPPO |
| R1-2004545 |
Other outstanding resource allocation issues |
Ericsson |
| R1-2004597 |
Remaining details of pre-emption |
Huawei, HiSilicon |
| 7.2.4.3 |
Sidelink synchronization mechanism |
|
| R1-2003311 |
Remaining details of Sidelink synchronization mechanism |
Nokia, Nokia Shanghai Bell |
| R1-2003381 |
Remaining issues on sidelink synchronization mechanism |
vivo |
| R1-2003496 |
Remaining details of sidelink synchronization mechanisms |
Huawei, HiSilicon |
| R1-2003564 |
Discussion on NR sidelink synchronization mechanism |
LG Electronics |
| R1-2003574 |
Remaining issues of Synchronization |
ZTE, Sanechips |
| R1-2003614 |
Remaining issues on sidelink synchronization mechanism in NR V2X |
CATT |
| R1-2003615 |
Feature lead summary#1 on AI 7.2.4.3 Sidelink synchronization mechanism |
Moderator (CATT) |
| R1-2003616 |
Feature lead summary#2 on AI 7.2.4.3 Sidelink synchronization mechanism |
Moderator (CATT) |
| R1-2003617 |
Feature lead summary#3 on AI 7.2.4.3 Sidelink synchronization mechanism |
Moderator (CATT) |
| R1-2003682 |
Discussion on sidelink based synchronization mechanism |
MediaTek Inc. |
| R1-2003875 |
On Synchronization Mechanisms for NR Sidelink |
Samsung |
| R1-2003951 |
Remaining issues on sidelink synchronization mechanisms |
CMCC |
| R1-2003992 |
Remaining issues in synchronization mechanism for NR V2X |
Spreadtrum Communications |
| R1-2004072 |
Remaining issues of synchronization for NR-V2X |
OPPO |
| R1-2004218 |
Remaining Details of PSBCH TDD Configuration Indication |
Apple |
| R1-2004329 |
Remaining issues on synchronization mechanism for NR sidelink |
Sharp |
| R1-2004386 |
Remaining issues on sidelink synchronization mechanism |
NTT DOCOMO, INC. |
| R1-2004453 |
Syncronisation details for NR-V2X |
Qualcomm Incorporated |
| R1-2004546 |
Synchronization mechanism for NR SL |
Ericsson |
| R1-2004999 |
LS on sidelink synchronization timing reference |
RAN1, CATT |
| R1-2005098 |
LS on sidelink synchronization timing reference |
RAN1, CATT |
| R1-2005099 |
Text proposal from Email discussion thread #01 for AI 7.2.4.3 Sidelink synchronization mechanism |
Moderator (CATT) |
| R1-2005100 |
Text proposal from Email discussion thread #02 for AI 7.2.4.3 Sidelink synchronization mechanism |
Moderator (CATT) |
| R1-2005101 |
Text proposal from Email discussion thread #03 for AI 7.2.4.3 Sidelink synchronization mechanism |
Moderator (CATT) |
| R1-2005103 |
Text proposal from Email discussion thread #02 for AI 7.2.4.3 Sidelink synchronization mechanism |
Moderator (CATT) |
| R1-2005104 |
Text proposal from Email discussion thread #03 for AI 7.2.4.3 Sidelink synchronization mechanism |
Moderator (CATT) |
| 7.2.4.4 |
In-device coexistence between LTE and NR sidelinks |
|
| R1-2003312 |
Remaining details of In-device coexistence between LTE and NR sidelinks |
Nokia, Nokia Shanghai Bell |
| R1-2003382 |
Remaining issues on In-device coexistence between NR and LTE sidelinks |
vivo |
| R1-2003497 |
Remaining details of in-device coexistence between LTE and NR sidelinks |
Huawei, HiSilicon |
| R1-2003551 |
Remaining issues of in-device coexistence |
ZTE, Sanechips |
| R1-2003565 |
Discussion on in-device coexistence between LTE and NR sidelinks |
LG Electronics |
| R1-2003876 |
On In-device Coexistence between LTE and NR Sidelink |
Samsung |
| R1-2004076 |
Remaining issues and TPs for in-device coexistence |
OPPO |
| R1-2004454 |
Corrections for in-device coexistence between LTE and NR sidelink |
Qualcomm Incorporated |
| R1-2004455 |
FL Summary of In-device Coexistence Aspects in NR-V2X |
Qualcomm Incorporated |
| R1-2004547 |
In-device coexistence between LTE and NR sidelinks |
Ericsson |
| R1-2005000 |
Text Proposals for In-device Coexistence Aspects in NR-V2X |
Moderator (Qualcomm) |
| 7.2.4.5 |
Physical layer procedures for sidelink |
|
| R1-2003313 |
Remaining details of Physical layer procedures for sidelink |
Nokia, Nokia Shanghai Bell |
| R1-2003383 |
Remaining issues on physical layer procedure for NR sidelink |
vivo |
| R1-2003498 |
Remaining details of physical layer procedures for sidelink |
Huawei, HiSilicon |
| R1-2003552 |
Remaining issues on PHY procedures for Rel-16 sidelink |
ZTE, Sanechips |
| R1-2003566 |
Discussion on physical layer procedure for NR sidelink |
LG Electronics |
| R1-2003569 |
Feature lead summary#1 for AI 7.2.4.5 Physical layer procedures for sidelink |
Moderator (LG Electronics) |
| R1-2003618 |
Remaining issues on physical layer procedures for NR V2X |
CATT |
| R1-2003715 |
Remaining Issues in Physical Layer Procedures for NR V2X |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2003736 |
Remaining opens of physical layer procedures for NR V2X sidelink design |
Intel Corporation |
| R1-2003827 |
Remaining issues on physical layer procedures for NR sidelink |
Lenovo, Motorola Mobility |
| R1-2003877 |
On Physical Layer Procedures for NR Sidelink |
Samsung |
| R1-2003943 |
Remaining issue on physical layer procedures for sidelink in NR V2X |
Panasonic Corporation |
| R1-2003952 |
Remaining issues on physical layer procedures for sidelink |
CMCC |
| R1-2003993 |
Remaining issues in physical layer procedures for sidelink |
Spreadtrum Communications |
| R1-2004044 |
Remaining issues on prioritization rule for NR V2X |
Fujitsu |
| R1-2004073 |
Remaining issues of physical layer procedure for NR-V2X |
OPPO |
| R1-2004219 |
Remaining Issues of Physical Layer Procedures for NR V2X |
Apple |
| R1-2004276 |
Remaining details on physical procedures for sidelink |
Futurewei |
| R1-2004296 |
Remaining Issues on Physical Layer Procedures for NR V2X |
InterDigital, Inc. |
| R1-2004330 |
Remaining issues on physical layer procedures for NR sidelink |
Sharp |
| R1-2004345 |
Remaining issues on sidelink physical layer procedure on NR V2X |
ASUSTeK |
| R1-2004387 |
Remaining issues on sidelink physical layer procedure |
NTT DOCOMO, INC. |
| R1-2004456 |
Physical layer procedures for sidelink |
Qualcomm Incorporated |
| R1-2004548 |
Physical layer procedures for NR sidelink |
Ericsson |
| R1-2004906 |
[Draft] LS reply to RAN2 on Cast type indication and MAC agreements |
LG Electronics |
| R1-2004916 |
LS reply to RAN2 on Cast type indication and MAC agreements |
RAN1, LG Electronics |
| R1-2004930 |
Feature lead summary#2 for AI 7.2.4.5 Physical layer procedures for sidelink |
Moderator (LG Electronics) |
| R1-2004931 |
Text proposal from Email discussion thread #1 for AI 7.2.4.5 Physical layer procedures for sidelink |
Moderator (LG Electronics) |
| R1-2004932 |
Text proposal from Email discussion thread #2 for AI 7.2.4.5 Physical layer procedures for sidelink |
Moderator (LG Electronics) |
| R1-2004933 |
Text proposal from Email discussion thread #3 for AI 7.2.4.5 Physical layer procedures for sidelink |
Moderator (LG Electronics) |
| R1-2004934 |
Text proposal from Email discussion thread #4 for AI 7.2.4.5 Physical layer procedures for sidelink |
Moderator (LG Electronics) |
| 7.2.4.6 |
QoS management for sidelink |
|
| R1-2003314 |
Remaining details of QoS management for sidelink |
Nokia, Nokia Shanghai Bell |
| R1-2003384 |
Remaining issues on QoS management for sidelink |
vivo |
| R1-2003499 |
Remaining details of QoS management for NR sidelink |
Huawei, HiSilicon |
| R1-2003553 |
Remaining issues on QoS |
ZTE, Sanechips |
| R1-2003567 |
Discussion on QoS management for NR sidelink |
LG Electronics |
| R1-2003619 |
Remaining issues on QoS management in NR V2X |
CATT |
| R1-2003878 |
On QoS Management for NR Sidelink |
Samsung |
| R1-2004077 |
Remaining open issues on QoS |
OPPO |
| R1-2004220 |
Remaining Issues of Sidelink QoS Management |
Apple |
| R1-2004297 |
Remaining Issues on Congestion control and QoS Management for NR-V2X |
InterDigital, Inc. |
| R1-2004549 |
QoS management for NR sidelink |
Ericsson |
| R1-2004663 |
Summary#1 for AI 7.2.4.6 QoS management for sidelink |
Moderator (Nokia) |
| R1-2004664 |
Summary#2 for AI 7.2.4.6 QoS management for sidelink |
Moderator (Nokia) |
| 7.2.4.7 |
Support of NR Uu controlling LTE sidelink |
|
| R1-2003315 |
Remaining details of Support of NR Uu controlling LTE sidelink |
Nokia, Nokia Shanghai Bell |
| R1-2003385 |
Remaining issues on support of NR Uu controlling LTE sidelink |
vivo |
| R1-2003500 |
Remaining details of NR Uu control for LTE sidelink |
Huawei, HiSilicon |
| R1-2003554 |
Remaining issues on NR Uu control LTE sidelink |
ZTE, Sanechips |
| R1-2003568 |
Discussion on NR Uu controlling LTE sidelink |
LG Electronics |
| R1-2003808 |
Remaining details of cross-RAT scheduling |
Futurewei |
| R1-2004078 |
Open loop power control for NR Uu controlling LTE sidelink |
OPPO |
| R1-2004388 |
Remaining issues on NR Uu controlling LTE SL |
NTT DOCOMO, INC. |
| R1-2004550 |
NR UU controlling LTE sidelink transmissions |
Ericsson |
| R1-2004722 |
FL summary #1 on NR Uu scheduling LTE sidelink |
Moderator (FUTUREWEI) |
| R1-2004955 |
Text Proposal for TS36.212 to clarify values of SPS activation/release in DCI format 5A |
Moderator (FUTUREWEI) |
| 7.2.4.8 |
Other |
|
| R1-2003386 |
Remaining aspects for NR V2X |
vivo |
| R1-2003575 |
Consideration of Sidelink Communication between in coverage and out of coverage UE |
ZTE, Sanechips |
| R1-2004079 |
Discussion on priority setting for higher layer contents |
OPPO |
| R1-2004298 |
Remaining Issues on Sidelink RLF |
InterDigital, Inc. |
| R1-2004551 |
Remaining details on resource pool determination |
Ericsson |
| R1-2004598 |
Remaining details of sidelink RRC Parameter List |
Huawei, HiSilicon |
| 7.2.5 |
Maintenance of Physical Layer Enhancements for NR URLLC (incl.maintenance for IIoT) |
|
| R1-2005086 |
Session notes for 7.2.5 (Maintenance of Physical Layer Enhancements for NR URLLC/IIoT) |
Ad-hoc Chair (Samsung) |
| 7.2.5.1 |
PDCCH enhancements |
|
| R1-2003317 |
Remaining issues on PDCCH enhancements for NR URLLC |
ZTE |
| R1-2003387 |
PDCCH enhancements for URLLC |
vivo |
| R1-2003439 |
Remaining Issue of PDCCH Enhancements for NR URLLC |
Ericsson |
| R1-2003525 |
Corrections on PDCCH enhancement for URLLC |
Huawei, HiSilicon |
| R1-2003577 |
Maintenance of Rel-16 URLLC PDCCH enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2003620 |
Remaining issues on PDCCH enhancements |
CATT |
| R1-2003684 |
Remaining issues on PDCCH enhancements |
MediaTek Inc. |
| R1-2003702 |
Remaining issue for TCI field |
ASUSTeK |
| R1-2003722 |
DCI Size Alignment |
Futurewei |
| R1-2003737 |
Remaining details on PDCCH enhancements for eURLLC |
Intel Corporation |
| R1-2003865 |
Remaining issues for PDCCH enhancements |
Samsung |
| R1-2003942 |
Remaining Issues on PDCCH Enhancements for URLLC |
Quectel |
| R1-2003944 |
Remaining issues on PDCCH enhancements for NR URLLC |
Panasonic Corporation |
| R1-2003979 |
Remaining issues of PDCCH enhancements for URLLC |
Spreadtrum Communications |
| R1-2004029 |
Remaining issues of PDCCH enhancements for NR URLLC |
LG Electronics |
| R1-2004114 |
PDCCH enhancements for URLLC |
OPPO |
| R1-2004221 |
Remaining Issues on PDCCH Enhancements for eURLLC |
Apple |
| R1-2004331 |
Remaining issues on PDCCH enhancements for NR URLLC |
Sharp |
| R1-2004389 |
Remaining issues for PDCCH enhancements for Rel.16 URLLC |
NTT DOCOMO, INC |
| R1-2004457 |
Remaining issues on PDCCH Enhancements for URLLC |
Qualcomm Incorporated |
| R1-2004522 |
Remaining issues on PDCCH enhancement for NR URLLC |
WILUS Inc. |
| R1-2004675 |
Feature lead summary#1 on PDCCH enhancements |
Moderator (Huawei) |
| R1-2004721 |
Feature lead summary#2 on PDCCH enhancements |
Moderator (Huawei) |
| R1-2004763 |
Summary #1 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design |
Moderator (Huawei) |
| R1-2004874 |
Discussion on PDCCH Enhancements for eURLLC |
Apple Inc. |
| R1-2004927 |
Summary #2 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design |
Moderator (Huawei) |
| R1-2004928 |
Summary #3 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design |
Moderator (Huawei) |
| R1-2004929 |
Summary #4 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design |
Moderator (Huawei) |
| R1-2005053 |
Summary #1 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-03] on remaining issues on enhanced PDCCH monitoring capability |
Moderator (Huawei) |
| R1-2005054 |
Summary #2 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-03] on remaining issues on enhanced PDCCH monitoring capability |
Moderator (Huawei) |
| R1-2005055 |
Summary #3 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-03] on remaining issues on enhanced PDCCH monitoring capability |
Moderator (Huawei) |
| R1-2005056 |
Text proposal for TS 38.213 Section 10.1 as outcome of issue D-1 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-03] |
Moderator (Huawei) |
| R1-2005057 |
Text proposal for TS 38.213 Section 10.1 as outcome of issue D-2 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-03] |
Moderator (Huawei) |
| R1-2005058 |
Text proposal for TS 38.213 Section 10 as outcome of issue C-6 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-03] |
Moderator (Huawei) |
| R1-2005059 |
Email discussion/approval [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design and proposed conclusion #1 |
Moderator (Huawei) |
| R1-2005060 |
Text proposal for TS 38.212 as outcome of issue A-3 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] |
Moderator (Huawei) |
| R1-2005061 |
Text proposal for TS 38.212 Section 7.3.1.0 as outcome of issue A-1 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] |
Moderator (Huawei) |
| R1-2005062 |
Text proposal for TS 38.212 Section 7.3.1.2.3 as outcome of issue A-5 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] |
Moderator (Huawei) |
| R1-2005063 |
Text proposal for TS 38.213 Section 9.1.3.1 as outcome of issue A-13 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] |
Moderator (Huawei) |
| R1-2005064 |
Text proposal for TS 38.213 Section 12 as outcome of issue A-12 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] |
Moderator (Huawei) |
| R1-2005065 |
Text proposals for TS 38.214 Section 5.1.6.2 & Section 5.1.6.3 as outcome of issue A-5 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] |
Moderator (Huawei) |
| R1-2005066 |
Summary #1 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on scaling PDCCH monitoring capability |
Moderator (Huawei) |
| R1-2005067 |
Summary #2 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on scaling PDCCH monitoring capability |
Moderator (Huawei) |
| R1-2005068 |
Text proposal for TS 38.213 Section 10.1 as outcome of issue C-3 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-02] |
Moderator (Huawei) |
| R1-2005069 |
Text proposal for TS 38.213 Section 10.1 as outcome of issue C-4 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-02] |
Moderator (Huawei) |
| R1-2005115 |
Summary #3 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on scaling PDCCH monitoring capability |
Moderator (Huawei) |
| R1-2005116 |
Text proposal for TS 38.213 Section 10 & Section 10.1 as outcome of issue C-1 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-02] |
Moderator (Huawei) |
| R1-2005117 |
Text proposal for TS 38.213 Section 10.1 as outcome of issue C-2 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-02] |
Moderator (Huawei) |
| 7.2.5.2 |
UCI enhancements |
|
| R1-2003318 |
Remaining issues on UL control enhancements for NR URLLC |
ZTE |
| R1-2003388 |
UCI enhancements for URLLC |
vivo |
| R1-2003440 |
Remaining Issue of UCI Enhancements for NR URLLC |
Ericsson |
| R1-2003528 |
Corrections on UCI enhancement |
Huawei, HiSilicon |
| R1-2003578 |
Maintenance of Rel-16 URLLC UCI enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2003621 |
Remaining issues on UCI enhancements |
CATT |
| R1-2003685 |
Remaining issues on UCI enhancements |
MediaTek Inc. |
| R1-2003708 |
Remaining Issues on UCI Enhancements for URLLC |
NEC |
| R1-2003738 |
Remaining details on UCI enhancements for eURLLC |
Intel Corporation |
| R1-2003814 |
Remaining issue on UCI enhancement |
Panasonic Corporation |
| R1-2003866 |
Remaining issues for UCI enhancements |
Samsung |
| R1-2003920 |
Discussion on remaining issues on UCI enhancement for URLLC |
Beijing Xiaomi Mobile Software |
| R1-2003953 |
Remaining issues on UCI enhancements for URLLC |
CMCC |
| R1-2003975 |
UCI enhancements |
ETRI |
| R1-2003980 |
Remaining Issues of UCI Enhancements for URLLC |
Spreadtrum Communications |
| R1-2004030 |
Remaining issues of UCI enhancements for NR URLLC |
LG Electronics |
| R1-2004045 |
Remaining issues on UCI enhancements for URLLC |
Fujitsu |
| R1-2004115 |
UCI enhancements for URLLC |
OPPO |
| R1-2004222 |
Remaining Issues on UCI Enhancements for eURLLC |
Apple |
| R1-2004271 |
UCI Enhancements for URLLC |
InterDigital, Inc. |
| R1-2004339 |
Remaining issue on the HARQ-ACK/PUSCH priority |
ITRI |
| R1-2004390 |
Remaining issues for UCI enhancement for Rel-16 URLLC |
NTT DOCOMO, INC |
| R1-2004458 |
Remaining issues on UCI Enhancements for URLLC |
Qualcomm Incorporated |
| R1-2004523 |
Remaining issues on UCI enhancement for NR URLLC |
WILUS Inc. |
| R1-2004574 |
Discussion on multiplexing UCI of same type on a PUSCH |
ASUSTeK |
| R1-2004674 |
Summary#1 on UCI enhancements for R16 URLLC |
Moderator (OPPO) |
| R1-2004779 |
Summary of email thread [101-e-NR-L1enh_URLLC-UCI_Enh-01] |
Moderator (OPPO) |
| R1-2004780 |
Summary of email thread [101-e-NR-L1enh_URLLC-UCI_Enh-02] |
Moderator (OPPO) |
| R1-2004781 |
Summary of email thread [101-e-NR-L1enh_URLLC-UCI_Enh-03] |
Moderator (OPPO) |
| R1-2004918 |
Summary#2 of email thread [101-e-NR-L1enh_URLLC-UCI_Enh-01] |
Moderator (OPPO) |
| R1-2004919 |
Summary#2 of email thread [101-e-NR-L1enh_URLLC-UCI_Enh-02] |
Moderator (OPPO) |
| R1-2004920 |
Summary#2 of email thread [101-e-NR-L1enh_URLLC-UCI_Enh-03] |
Moderator (OPPO) |
| 7.2.5.3 |
PUSCH enhancements |
|
| R1-2003319 |
Remaining issues on PUSCH enhancements for NR URLLC |
ZTE |
| R1-2003389 |
PUSCH enhancements for URLLC |
vivo |
| R1-2003441 |
Remaining Issue of PUSCH Enhancements for NR URLLC |
Ericsson |
| R1-2003529 |
Corrections on PUSCH enhancement |
Huawei, HiSilicon |
| R1-2003579 |
Maintenance of PUSCH enhancements for Rel-16 NR URLLC |
Nokia, Nokia Shanghai Bell |
| R1-2003622 |
Remaining issues on PUSCH enhancements |
CATT |
| R1-2003739 |
Corrections on PUSCH enhancements for URLLC |
Intel Corporation |
| R1-2003815 |
Remaining issues on URLLC PUSCH enhancement |
Panasonic Corporation |
| R1-2003867 |
Remaining issues for PUSCH enhancements |
Samsung |
| R1-2003976 |
PUSCH enhancements |
ETRI |
| R1-2003986 |
Discussion on PUSCH enhancements for URLLC |
Spreadtrum Communications |
| R1-2004031 |
Remaining issues of PUSCH enhancements for NR URLLC |
LG Electronics |
| R1-2004046 |
Remaining issues on PUSCH enhancements for URLLC |
Fujitsu |
| R1-2004116 |
PUSCH enhancements for URLLC |
OPPO |
| R1-2004223 |
Remaining Issues on PUSCH enhancements for eURLLC |
Apple |
| R1-2004224 |
Feature lead summary on PUSCH enhancements for NR eURLLC (AI 7.2.5.3) |
Moderator (Apple) |
| R1-2004332 |
Remaining issues on PUSCH enhancements for NR URLLC |
Sharp |
| R1-2004391 |
Remaining issues for PUSCH enhancements for Rel.16 URLLC |
NTT DOCOMO, INC |
| R1-2004459 |
Remaining issues on PUSCH enhancements for URLLC |
Qualcomm Incorporated |
| R1-2004524 |
Remaining issues on PUSCH enhancement for NR URLLC |
WILUS Inc. |
| R1-2004572 |
Remaining issue of PUSCH enhancements for NR URLLC |
ASUSTeK |
| R1-2004739 |
Summary of [101-e-NR-L1enh-URLLC-PUSCH-01] (AI 7.2.5.3) |
Moderator (Apple Inc.) |
| R1-2004740 |
Final Summary of [101-e-NR-L1enh-URLLC-PUSCH-02] (AI 7.2.5.3) Moderator (Apple Inc.) |
Moderator (Apple Inc.) |
| R1-2004741 |
Final summary of [101-e-NR-L1enh-URLLC-PUSCH-03] (AI 7.2.5.3) |
Moderator (Apple Inc.) |
| R1-2004742 |
Summary of [101-e-NR-L1enh-URLLC-PUSCH-04] (AI 7.2.5.3) |
Moderator (Apple Inc.) |
| R1-2004773 |
Summary #1 of [101-e-NR-L1enh-URLLC-PUSCH-02] (AI 7.2.5.3) |
Moderator (Apple Inc.) |
| R1-2004774 |
Summary #1 of [101-e-NR-L1enh-URLLC-PUSCH-03] (AI 7.2.5.3) |
Moderator (Apple Inc.) |
| R1-2004981 |
Summary #2 of [101-e-NR-L1enh-URLLC-PUSCH-02] (AI 7.2.5.3) |
Moderator (Apple Inc.) |
| R1-2004982 |
Summary #2 of [101-e-NR-L1enh-URLLC-PUSCH-03] (AI 7.2.5.3) |
Moderator (Apple Inc.) |
| 7.2.5.4 |
Enhancements to scheduling/HARQ |
|
| R1-2003320 |
Remaining issues on scheduling/HARQ enhancements for NR URLLC |
ZTE |
| R1-2003390 |
Enhancement for Scheduling/HARQ |
vivo |
| R1-2003442 |
Remaining Issue of Scheduling/HARQ for NR URLLC |
Ericsson |
| R1-2003580 |
Maintenance of Rel-16 URLLC scheduling/HARQ enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2004117 |
Ehancements to scheduling and HARQ |
OPPO |
| R1-2004156 |
Corrections on operation of out-of-order |
Huawei, HiSilicon |
| R1-2004392 |
Remaining issue for scheduling and HARQ enhancements for URLLC |
NTT DOCOMO, INC |
| R1-2004743 |
Summary of the remaining issues on HARQ and scheduling enhancements for URLLC |
Moderator (Qualcomm) |
| R1-2004839 |
Summary of email discussion [101-e-NR-L1enh-URLLC-HARQ&Scheduling-01] |
Moderator (Qualcomm) |
| R1-2004840 |
Summary of email discussion [101-e-NR-L1enh-URLLC-HARQ&Scheduling-03] |
Moderator (Qualcomm) |
| R1-2004977 |
Summary#2 of email discussion [101-e-NR-L1enh-URLLC-HARQ&Scheduling-01] |
Moderator (Qualcomm) |
| R1-2004978 |
Summary#3 of email discussion [101-e-NR-L1enh-URLLC-HARQ&Scheduling-01] |
Moderator (Qualcomm) |
| R1-2004979 |
Summary#2 of email discussion [101-e-NR-L1enh-URLLC-HARQ&Scheduling-03] |
Moderator (Qualcomm) |
| R1-2004980 |
Summary#3 of email discussion [101-e-NR-L1enh-URLLC-HARQ&Scheduling-03] |
Moderator (Qualcomm) |
| R1-2005071 |
Summary#3 of email discussion [101-e-NR-L1enh-URLLC-HARQ&Scheduling-01] |
Moderator (Qualcomm) |
| R1-2005072 |
Summary#4 of email discussion [101-e-NR-L1enh-URLLC-HARQ&Scheduling-03] |
Moderator (Qualcomm) |
| R1-2005074 |
Summary #1 of email discussion [101-e-NR-L1enh-URLLC-HARQ&Scheduling-02] |
Moderator (Qualcomm) |
| R1-2005075 |
Endorsed TPs of email discussion [101-e-NR-L1enh-URLLC-HARQ&Scheduling-01] |
Moderator (Qualcomm) |
| R1-2005076 |
Endorsed TPs of email discussion [101-e-NR-L1enh-URLLC-HARQ&Scheduling-02] |
Moderator (Qualcomm) |
| R1-2005077 |
Endorsed TPs of email discussion [101-e-NR-L1enh-URLLC-HARQ&Scheduling-03] |
Moderator (Qualcomm) |
| 7.2.5.5 |
Enhanced inter UE Tx prioritization/multiplexing |
|
| R1-2003321 |
Remaining issues on UL inter-UE multiplexing between eMBB and URLLC |
ZTE |
| R1-2003391 |
UL inter UE Tx prioritization for URLLC |
vivo |
| R1-2003394 |
Summary of UL inter UE Tx prioritization |
Moderator (vivo) |
| R1-2003443 |
Remaining Issue of Inter-UE Prioritization and Multiplexing of UL Transmissions |
Ericsson |
| R1-2003527 |
Corrections on UL inter-UE multiplexing |
Huawei, HiSilicon |
| R1-2003581 |
Maintenance of Rel-16 URLLC Enhanced inter UE Tx prioritization/multiplexing |
Nokia, Nokia Shanghai Bell |
| R1-2003623 |
Remaining issues on inter-UE UL multiplexing |
CATT |
| R1-2003686 |
Remaining issues on enhanced inter-UE Tx prioritization/multiplexing |
MediaTek Inc. |
| R1-2003709 |
Remaining Issues on Enhanced Inter-UE Tx Prioritisaion / Multiplexing |
NEC |
| R1-2003740 |
Remaining issues on enhanced inter-UE multiplexing |
Intel Corporation |
| R1-2003868 |
Remaining issues for inter-UE multiplexing |
Samsung |
| R1-2003981 |
Remaining issues of enhanced inter UE Tx prioritization/multiplexing |
Spreadtrum Communications |
| R1-2004032 |
Remaining issues of UL inter UE Tx prioritization |
LG Electronics |
| R1-2004118 |
Inter UE Tx prioritization and multiplexing |
OPPO |
| R1-2004185 |
Remaining issues on Inter-UE Multiplexing for eURLLC |
Sony |
| R1-2004225 |
Remaining Issues on Inter-UE Cancellation for eURLLC |
Apple |
| R1-2004272 |
Inter-UE prioritization/multiplexing |
InterDigital, Inc. |
| R1-2004371 |
Remaining issues of enhanced inter UE Tx prioritization/multiplexing |
Motorola Mobility, Lenovo |
| R1-2004393 |
Remaining issue on inter-UE Tx multiplexing/prioritization |
NTT DOCOMO, INC |
| R1-2004460 |
Remaining issues on uplink Inter-UE Tx Multiplexing and Prioritization |
Qualcomm Incorporated |
| R1-2004525 |
Remaining issues on inter-UE multiplexing for NR URLLC |
WILUS Inc. |
| R1-2004728 |
Summary#2 of UL inter UE Tx prioritization |
Moderator (vivo) |
| R1-2004734 |
Summary of [101-e-NR-L1enh-URLLC-InterUE-01] |
Moderator (vivo) |
| R1-2004735 |
Summary of [101-e-NR-L1enh-URLLC-InterUE-02] |
Moderator (vivo) |
| R1-2004736 |
Summary of [101-e-NR-L1enh-URLLC-InterUE-03] |
Moderator (vivo) |
| 7.2.5.6 |
Enhanced UL configured grant transmission |
|
| R1-2003322 |
Remaining issues on enhancements for UL configured grant transmission |
ZTE |
| R1-2003392 |
Enhanced UL configured grant transmissions for URLLC |
vivo |
| R1-2003395 |
Summary of enhanced UL configured grant transmission |
Moderator (vivo) |
| R1-2003444 |
Remaining Issue of Enhancements to UL Configured Grant Transmission for NR URLLC |
Ericsson |
| R1-2003526 |
Corrections on configured grant transmission |
Huawei, HiSilicon |
| R1-2003624 |
Remaining issues on enhanced UL configured grant transmission |
CATT |
| R1-2004033 |
Remaining issues of Enhanced UL configured grant transmission for NR URLLC |
LG Electronics |
| R1-2004119 |
Configured grant enhancements for URLLC |
OPPO |
| R1-2004226 |
Remaining Issues in Enhanced Configured Grant Transmission |
Apple |
| R1-2004757 |
Email discussion #01 for enhanced configured grant transmission |
Moderator (vivo) |
| R1-2004985 |
Discussion on cancellation and replacement for URLLC |
Apple Inc. |
| R1-2005052 |
Email discussion outcome for enhanced configured grant transmission |
Moderator (vivo) |
| R1-2005078 |
LS on Intra-UE Prioritization for data with different priorities |
RAN1, vivo |
| 7.2.5.7 |
Other |
|
| R1-2003323 |
Remaining issues on SPS enhancements |
ZTE |
| R1-2003393 |
Other issues for URLLC |
vivo |
| R1-2003445 |
Remaining Issue of Other Enhancements for NR URLLC/IIoT |
Ericsson |
| R1-2003582 |
Maintenance of Rel-16 URLLC/IIoT SPS enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2003625 |
Remaining issues on IIoT |
CATT |
| R1-2003710 |
Remaining issues on DL SPS enhancement for URLLC |
NEC |
| R1-2003741 |
Corrections for DL SPS and intra-UE prioritization involving CG PUSCH |
Intel Corporation |
| R1-2003869 |
Remaining issues for Others |
Samsung |
| R1-2003982 |
Remaining issues on enhanced DL SPS for IIoT |
Spreadtrum Communications |
| R1-2004034 |
Remaining issues of other aspects for URLLC/IIOT |
LG Electronics |
| R1-2004035 |
Summary on maintenance of other aspects for URLLC/IIOT |
Moderator (LG Electronics) |
| R1-2004120 |
DL SPS enhancement |
OPPO |
| R1-2004125 |
Remaining issues on intra-UE prioritization for URLLC |
MediaTek Inc. |
| R1-2004184 |
Discussion on RAN2 LS on Intra-UE Prioritization |
Sony |
| R1-2004227 |
Remaining Issues in eURLLC/IIoT |
Apple |
| R1-2004394 |
Remaining issues for SPS enhancement for Rel-16 URLLC |
NTT DOCOMO, INC |
| R1-2004461 |
Remaining issues on uplink collision handling and SPS for URLLC |
Qualcomm Incorporated |
| R1-2004611 |
Corrections on other aspects for URLLC/IIOT enhancements |
Huawei, HiSilicon |
| R1-2004714 |
Summary #2 on maintenance of other aspects for URLLC/IIOT |
Moderator (LG Electronics) |
| R1-2004803 |
Summary of [101-e-NR-L1enh-URLLC-IIoTenh-01] |
Moderator (LG Electronics) |
| R1-2004804 |
Summary of [101-e-NR-L1enh-URLLC-IIoTenh-02] |
Moderator (LG Electronics) |
| R1-2004805 |
Summary of [101-e-NR-L1enh-URLLC-IIoTenh-03] |
Moderator (LG Electronics) |
| R1-2004806 |
Summary of [101-e-NR-L1enh-URLLC-IIoTenh-04] |
Moderator (LG Electronics) |
| R1-2004807 |
[Draft] Reply LS on Intra-UE prioritization |
LG Electronics |
| R1-2004899 |
Reply LS on Intra-UE prioritization |
RAN1, LG Electronics |
| R1-2004973 |
Summary#2 of [101-e-NR-L1enh-URLLC-IIoTenh-01] |
Moderator (LG Electronics) |
| R1-2004974 |
Summary#2 of [101-e-NR-L1enh-URLLC-IIoTenh-02] |
Moderator (LG Electronics) |
| R1-2004975 |
Summary#2 of [101-e-NR-L1enh-URLLC-IIoTenh-03] |
Moderator (LG Electronics) |
| R1-2004976 |
Summary#2 of [101-e-NR-L1enh-URLLC-IIoTenh-04] |
Moderator (LG Electronics) |
| 7.2.6 |
Maintenance of Enhancements on MIMO for NR |
|
| R1-2005087 |
Session notes for 7.2.6 (Maintenance of Enhancements on MIMO for NR) |
Ad-hoc Chair (Samsung) |
| 7.2.6.1 |
CSI Enhancement for MU-MIMO Support |
|
| R1-2003396 |
On remaining issues on MU CSI |
vivo |
| R1-2003468 |
Maintenance of CSI enhancement for MU-MIMO |
ZTE |
| R1-2003530 |
Remaining issues on MU-CSI in R16 |
Huawei, HiSilicon |
| R1-2003626 |
Remaining issues on CSI enhancement for MU-MIMO |
CATT |
| R1-2003879 |
On maintenance of Rel.16 MU CSI enhancements |
Samsung |
| R1-2003880 |
Feature lead summary for MU-MIMO CSI |
Moderator (Samsung) |
| R1-2003927 |
TP on enhanced Type II port selection codebook |
LG Electronics |
| R1-2004228 |
Remaining issues for Rel-16 Type II CSI enhancement |
Apple |
| R1-2004264 |
Maintenance on Rel-16 CSI enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2004372 |
Maintenance on MU-CSI Enhancements |
Motorola Mobility, Lenovo |
| R1-2004462 |
Remaining issues on MU-CSI enhancement |
Qualcomm Incorporated |
| R1-2004527 |
Discussion on MU CSI |
Ericsson |
| R1-2004712 |
TP for eMIMO MU-CSI thread #1 |
Moderator (Samsung) |
| R1-2004713 |
Feature lead summary for MU-MIMO CSI thread #2 |
Moderator (Samsung) |
| 7.2.6.2 |
Enhancements on Multi-TRP/Panel Transmission |
|
| R1-2003397 |
On remaining issues on M-TRP |
vivo |
| R1-2003469 |
Maintenance of multi-TRP enhancements |
ZTE |
| R1-2003531 |
Remaining issues on multi-TRP in R16 |
Huawei, HiSilicon |
| R1-2003627 |
Discussion on remaining issues of multi-TRP/panel transmission |
CATT |
| R1-2003660 |
Remaining issues on multi-TRP transmission |
MediaTek Inc. |
| R1-2003742 |
Corrections to multi-TRP |
Intel Corporation |
| R1-2003819 |
Remaining issues on multi-TRP/panel transmission |
Lenovo, Motorola Mobility |
| R1-2003881 |
On Rel.16 multi-TRP/panel transmission |
Samsung |
| R1-2003928 |
Text proposals on enhancements on multi-TRP/panel transmission |
LG Electronics |
| R1-2003954 |
Remaining issues on multi-TRP/panel transmission |
CMCC |
| R1-2003987 |
Discussion on remaining issues of multi-TRP operation |
Spreadtrum Communications |
| R1-2004047 |
Text proposals for enhancements on multi-TRP and panel Transmission |
OPPO |
| R1-2004229 |
Remaining issues for Multi-TRP enhancement |
Apple |
| R1-2004265 |
Maintenance of Rel-16 Multi-TRP operation |
Nokia, Nokia Shanghai Bell |
| R1-2004311 |
Remaining issues on multi-TRP transmission |
NEC |
| R1-2004370 |
FL summary for Multi-TRP/Panel Transmission |
Moderator (OPPO) |
| R1-2004395 |
Remaining issues on multi-TRP/panel transmission |
NTT DOCOMO, INC |
| R1-2004432 |
Remaining issues on Multi-TRP/Panel Transmission |
Ericsson |
| R1-2004463 |
Multi-TRP Enhancements |
Qualcomm Incorporated |
| R1-2004592 |
Clarification on Multi-TRP URLLC Scheme 4 |
Convida Wireless |
| R1-2004719 |
FL Summary #2 for Multi-TRP/Panel Transmission |
Moderator (OPPO) |
| R1-2004770 |
Text Proposal for TS 38.211 in [101-e-NR-eMIMO-multiTRP-03] |
Moderator (OPPO) |
| R1-2004771 |
Text Proposal for TS 38.214 in [101-e-NR-eMIMO-multiTRP-03] |
Moderator (OPPO) |
| R1-2004772 |
Summary of email thread [101-e-NR-eMIMO-multiTRP-03] |
Moderator (OPPO) |
| R1-2004907 |
Text Proposal for TS 38.214 in [101-e-NR-eMIMO-multiTRP-02] |
Moderator (OPPO) |
| R1-2004908 |
Summary of email thread [101-e-NR-eMIMO-multiTRP-02] |
Moderator (OPPO) |
| R1-2004924 |
Text Proposal for TS 38.213 in [101-e-NR-eMIMO-multiTRP-02] |
Moderator (OPPO) |
| R1-2004925 |
Text Proposal for TS 38.214 in [101-e-NR-eMIMO-multiTRP-01] |
Moderator (OPPO) |
| R1-2004926 |
Summary of email thread [101-e-NR-eMIMO-multiTRP-01] |
Moderator (OPPO) |
| 7.2.6.3 |
Enhancements on Multi-beam Operation |
|
| R1-2003398 |
On remaining issues on Multi Beam |
vivo |
| R1-2003470 |
Maintenance of multi-beam operation |
ZTE |
| R1-2003532 |
Remaining issues on multi-beam enhancements in R16 |
Huawei, HiSilicon |
| R1-2003628 |
Remaining issues on multi-beam operation enhancement |
CATT |
| R1-2003661 |
Remaining issues on multi-beam operation |
MediaTek Inc. |
| R1-2003820 |
Remaining issues on multi-beam operation |
Lenovo, Motorola Mobility |
| R1-2003882 |
On Rel.16 support for multibeam operation |
Samsung |
| R1-2003929 |
Remaining issues on multi beam operation |
LG Electronics |
| R1-2003930 |
FL summary#1 on Rel-16 MB1 maintenance |
Moderator (LG Electronics) |
| R1-2003931 |
FL summary#2 on Rel-16 MB1 maintenance |
Moderator (LG Electronics) |
| R1-2003955 |
Remaining issues on multi-beam operation |
CMCC |
| R1-2003985 |
Discussion on remaining issues of multi-beam operation |
Spreadtrum Communications |
| R1-2004048 |
Remaining issues on Multi-beam Operation Enhancement |
OPPO |
| R1-2004186 |
Remaining issues on multi-beam operation |
Sony |
| R1-2004201 |
Remaining issues on multi-beam operation |
Ericsson |
| R1-2004230 |
Remaining issues on beam management enhancement |
Apple |
| R1-2004231 |
Feature Lead Summary #1 on L1-SINR and SCell BFR |
Apple |
| R1-2004232 |
Feature Lead Summary #2 on L1-SINR and SCell BFR |
Apple |
| R1-2004266 |
Maintenance of Rel-16 Beam Management |
Nokia, Nokia Shanghai Bell |
| R1-2004396 |
Remaining issues on multi-beam operation |
NTT DOCOMO, INC |
| R1-2004464 |
Enhancements on Multi-beam Operation |
Qualcomm Incorporated |
| R1-2004709 |
Feature Lead Summary #3 on L1-SINR and SCell BFR |
Moderator (Apple) |
| R1-2004790 |
Outcome of email thread [101-e-NR-eMIMO-MB1-01] |
Moderator (LG Electronics) |
| R1-2004791 |
Outcome of email thread [101-e-NR-eMIMO-MB1-02] |
Moderator (LG Electronics) |
| R1-2004792 |
Outcome of email thread [101-e-NR-eMIMO-MB1-03] |
Moderator (LG Electronics) |
| R1-2004793 |
TP for capturing outcome of email thread [101-e-NR-eMIMO-MB1-01] |
Moderator (LG Electronics) |
| R1-2004794 |
TP for capturing outcome of email thread [101-e-NR-eMIMO-MB1-02] |
Moderator (LG Electronics) |
| R1-2004795 |
TP for capturing outcome of email thread [101-e-NR-eMIMO-MB1-03] |
Moderator (LG Electronics) |
| R1-2004837 |
Text Proposal for MB2 email thread #1 |
Moderator (Apple) |
| R1-2004838 |
Text Proposal for MB2 email thread #2 |
Moderator (Apple) |
| 7.2.6.4 |
Full TX Power UL transmission |
|
| R1-2003399 |
On remaining issues on UL full power Tx |
vivo |
| R1-2003402 |
Feature lead summary on UL full power transmission |
Moderator (vivo) |
| R1-2003471 |
Maintenance of full power UL transmission |
ZTE |
| R1-2003533 |
Remaining issues on UL full power transmission in R16 |
Huawei, HiSilicon |
| R1-2003629 |
On UL full power transmission |
CATT |
| R1-2003662 |
Remaining issues on UL full power transmission |
MediaTek Inc. |
| R1-2003743 |
Correction to Full Tx Power UL Transmission |
Intel Corporation |
| R1-2003883 |
On UL full power transmission |
Samsung |
| R1-2003932 |
Text proposals on full Tx power UL transmission |
LG Electronics |
| R1-2003956 |
Discussion on full TX power UL transmission |
CMCC |
| R1-2003984 |
Discussion on remaining issues on full TX power for UL transmission |
Spreadtrum Communications |
| R1-2004049 |
Text proposals for full TX power UL transmission |
OPPO |
| R1-2004233 |
Remaining issues for UL Full Power transmission enhancement |
Apple |
| R1-2004267 |
Maintenance of Rel-16 Full TX Power UL transmission |
Nokia, Nokia Shanghai Bell |
| R1-2004346 |
Corrections for Full Power UL Transmission |
Ericsson |
| R1-2004397 |
Remaining issue on full Tx power UL transmission |
NTT DOCOMO, INC |
| R1-2004465 |
Remaining issues on full power UL transmission |
Qualcomm Incorporated |
| R1-2004708 |
Summary of prep email discussion on ULFPTx |
Moderator (vivo) |
| R1-2004797 |
Feature lead summary on [101-e-NR-eMIMO-ULFPTx-01] |
Moderator (vivo) |
| R1-2004798 |
Feature lead summary on [101-e-NR-eMIMO-ULFPTx-02] |
Moderator (vivo) |
| R1-2004799 |
Feature lead summary on [101-e-NR-eMIMO-ULFPTx-03] |
Moderator (vivo) |
| R1-2004886 |
Outcome of [101-e-NR-eMIMO-ULFPTx-02] Email discussion |
Moderator (vivo) |
| R1-2004887 |
Outcome of [101-e-NR-eMIMO-ULFPTx-03] Email discussion |
Moderator (vivo) |
| R1-2004900 |
Miscellaneous corrections on ULFPTx |
Moderator (vivo) |
| 7.2.6.5 |
Low PAPR RS |
|
| R1-2003400 |
On remaining issues on Low PAPR RS |
vivo |
| R1-2003534 |
Remaining issues on low PAPR sequence in R16 |
Huawei, HiSilicon |
| R1-2003663 |
Maintenance of low PAPR RS |
MediaTek Inc. |
| R1-2003707 |
Remaining issues on low PAPR RS |
Ericsson |
| R1-2003744 |
Corrections to Low PAPR RS |
Intel Corporation |
| R1-2004050 |
Text proposals for low PAPR RS |
OPPO |
| R1-2004268 |
Corrections on Low PAPR RS |
Nokia, Nokia Shanghai Bell |
| R1-2004466 |
Remaining issues on low PAPR RS |
Qualcomm Incorporated |
| R1-2004504 |
FL summary 1 of low PAPR RS |
Moderator (Ericsson) |
| R1-2004761 |
TP for eMIMO lowPAPR thread #1 |
Moderator (Ericsson) |
| R1-2004762 |
TP for eMIMO lowPAPR thread #2 |
Moderator (Ericsson) |
| 7.2.6.6 |
Other |
|
| R1-2003401 |
Discussion on P3 L1-SINR measurement |
vivo |
| R1-2003483 |
Preliminary views on further enhancement for NR MIMO |
ZTE |
| R1-2004051 |
Remaining issues on multi-TRP and panel Transmission |
OPPO |
| R1-2004234 |
On further MIMO enhancement |
Apple |
| R1-2004505 |
Critical MIMO issue from observations in field |
Ericsson |
| R1-2004613 |
Other open issues for Rel-16 MIMO |
Huawei, HiSilicon |
| 7.2.7.1 |
PDCCH-based power saving signal/channel |
|
| R1-2003403 |
Maintenance of PDCCH-based power saving signal |
vivo |
| R1-2003486 |
Remaining issues on WUS PDCCH |
ZTE |
| R1-2003518 |
Remaining issues on PDCCH based power saving |
Huawei, HiSilicon |
| R1-2003630 |
Remaining issues on the Power Saving Signals/Channels |
CATT |
| R1-2003664 |
Remaining issues on PDCCH-based power saving signal |
MediaTek Inc. |
| R1-2003745 |
Remaining details of PDCCH-based power saving signal/channel |
Intel Corporation |
| R1-2003884 |
Remaining issues for PDCCH-based power saving signal |
Samsung |
| R1-2003924 |
TP for further alignment with RAN2 specifications |
NEC |
| R1-2003957 |
Remaining issues on power saving signal/channel |
CMCC |
| R1-2003999 |
Clarification on power saving signal |
Spreadtrum Communications |
| R1-2004025 |
Remaining issues on PDCCH-based power saving signal/channel |
LG Electronics |
| R1-2004101 |
Remaining issues for Power saving signal |
OPPO |
| R1-2004320 |
Wake up indication for ON duration timer |
ASUSTeK |
| R1-2004357 |
Remaining issues for WUS |
Ericsson |
| R1-2004398 |
Maintenance for PDCCH-based power saving signal/channel |
NTT DOCOMO, INC. |
| R1-2004467 |
Remainign issues in power saving signal/channel |
Qualcomm Incorporated |
| R1-2004577 |
On open issues related to DCI format 2_6 |
Nokia, Nokia Shanghai Bell |
| R1-2004723 |
Preparation summary of PDCCH-based power saving signal/channel |
Moderator (CATT) |
| R1-2004724 |
Final summary of PDCCH-based power saving signal/channel |
Moderator (CATT) |
| R1-2004994 |
LS reply on DCP open issues |
RAN1, CATT |
| 7.2.7.2 |
Procedure of cross-slot scheduling power saving techniques |
|
| R1-2003404 |
Maintenance of procedure of cross-slot scheduling power saving techniques |
vivo |
| R1-2003487 |
Remaining issues on cross-slot scheduling power saving techniques |
ZTE |
| R1-2003519 |
Remaining issues on cross-slot scheduling based power saving |
Huawei, HiSilicon |
| R1-2003631 |
Remaining issues on Power saving scheme with cross-slot scheduling |
CATT |
| R1-2003665 |
Remaining issues on cross-slot scheduling adaptation |
MediaTek Inc. |
| R1-2003746 |
Remaining details of cross-slot scheduling for power saving |
Intel Corporation |
| R1-2003885 |
Remaining issues for cross-slot scheduling |
Samsung |
| R1-2003958 |
Remaining issues on cross-slot scheduling procedure |
CMCC |
| R1-2003994 |
Remaining issues on cross-slot scheduling |
Spreadtrum Communications |
| R1-2004026 |
Remaining issues on procedure of cross-slot scheduling power saving techniques |
LG Electronics |
| R1-2004102 |
Remaining issues for cross-slot scheduling |
OPPO |
| R1-2004187 |
Remaining issues on cross-slot scheduling for UE power saving |
Sony |
| R1-2004307 |
Remaining issues of cross-slot scheduling for UE power saving |
InterDigital |
| R1-2004358 |
Remaining issues for cross-slot scheduling |
Ericsson |
| R1-2004399 |
Maintenance for procedure of cross-slot scheduling power saving techniques |
NTT DOCOMO, INC. |
| R1-2004468 |
Remaining issues in cross-slot scheduling power saving |
Qualcomm Incorporated |
| R1-2004578 |
Procedure of cross-slot scheduling power saving techniques |
Nokia, Nokia Shanghai Bell |
| R1-2004669 |
Summary#1 for Procedure of cross-slot scheduling power saving techniques |
Moderator (MediaTek) |
| R1-2004765 |
Summary#2 for Procedure of cross-slot scheduling power saving techniques |
Moderator (MediaTek) |
| R1-2004971 |
Summary#3 for Procedure of cross-slot scheduling power saving techniques |
Moderator (MediaTek) |
| 7.2.7.3 |
UE adaptation to maximum number of MIMO layers |
|
| R1-2003488 |
On UE adaptation to maximum number of MIMO layers |
ZTE |
| R1-2003520 |
Remaining issues on UE adaptation to maximum MIMO layers |
Huawei, HiSilicon |
| R1-2004359 |
Remaining issues for MIMO layer signaling per BWP |
Ericsson |
| R1-2004579 |
On open issues for per-BWP DL MIMO layers |
Nokia, Nokia Shanghai Bell |
| R1-2004686 |
Summary of UE adaptation to maximum number of MIMO layers |
Moderator (vivo) |
| 7.2.7.4 |
Other |
|
| R1-2003405 |
Other issues for R16 UE power saving |
vivo |
| R1-2003489 |
Views on power saving enhancement |
ZTE |
| R1-2004360 |
UE power saving using search space set switching |
Ericsson |
| R1-2004607 |
Initial views on baseline assumptions for Rel-17 power saving enhancements |
Huawei, HiSilicon |
| 7.2.8 |
Maintenance of NR positioning support |
|
| R1-2004727 |
Summary on scope of NR positioning email discussions at RAN1#101-E |
Moderators (Intel, Ericsson, CATT, Qualcomm) |
| R1-2005091 |
Session notes for 7.2.8 (Maintenance of NR positioning support) |
Ad-Hoc Chair (Ericsson) |
| 7.2.8.1 |
DL Reference Signals for NR Positioning |
|
| R1-2003406 |
Discussion on remaining issues on DL RS for NR positioning |
vivo |
| R1-2003472 |
Maintenance of DL reference signals for NR positioning |
ZTE |
| R1-2003521 |
Finalizing DL PRS |
Huawei, HiSilicon |
| R1-2003632 |
Remaining issues on DL PRS for NR Positioning |
CATT |
| R1-2003716 |
Maintenance on DL reference signals for NR Positioning |
Nokia, Nokia Shanghai Bell |
| R1-2003886 |
DL reference signals for NR Positioning |
Samsung |
| R1-2004052 |
Remaining Issues on DL Positioning Reference Signal |
OPPO |
| R1-2004134 |
Remaining details of DL Reference signals for NR positioning |
LG Electronics |
| R1-2004469 |
Maintenance on DL Reference Signals for NR Positioning |
Qualcomm Incorporated |
| R1-2004643 |
Maintenance of DL reference signals for NR positioning |
Ericsson |
| R1-2004726 |
FL summary #1 on DL Reference Signals for NR Positioning |
Moderator (Intel Corporation) |
| R1-2004958 |
Draft LS on the UE DL PRS processing |
Intel |
| R1-2004959 |
LS on the UE DL PRS processing |
RAN1, Intel |
| R1-2004960 |
Summary of E-mail Discussion [101-e-NR-Pos-01] |
Intel Corporation |
| R1-2005046 |
Draft LS on Capturing UE DL PRS Processing Capability |
Intel |
| R1-2005047 |
LS on Capturing UE DL PRS Processing Capability |
RAN1, Intel |
| 7.2.8.2 |
UL Reference Signals for NR Positioning |
|
| R1-2003407 |
Discussion on remaining issues on UL RS for NR positioning |
vivo |
| R1-2003473 |
Maintenance of UL reference signals for NR positioning |
ZTE |
| R1-2003522 |
Finalizing SRS for NR positioning |
Huawei, HiSilicon |
| R1-2003633 |
Remaining issues on UL SRS for NR Positioning |
CATT |
| R1-2003887 |
UL reference signals for NR Positioning |
Samsung |
| R1-2003959 |
Remaining issues on UL SRS for positioning transmission |
CMCC |
| R1-2004053 |
Remaining Issues on UL Positioning Reference Signal |
OPPO |
| R1-2004135 |
Remaining details of UL Reference signals for NR positioning |
LG Electronics |
| R1-2004470 |
Maintenance on UL Reference Signals for NR Positioning |
Qualcomm Incorporated |
| R1-2004515 |
Discussion on staggered SRS for NR Positioning |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2004644 |
Maintenance of UL Reference Signals for NR Positioning |
Ericsson |
| R1-2004718 |
Feature lead summary for UL Reference Signals for NR Positioning |
Moderator (Ericsson) |
| R1-2004909 |
Output #1 of email discussion [101-e-NR-Pos-02] on DL PRS and UL SRS for NR positioning in rel16 maintenance |
Moderator (Ericsson) |
| R1-2005001 |
Output #2 of email discussion [101-e-NR-Pos-02] on DL PRS and UL SRS for NR positioning in rel16 maintenance |
Moderator (Ericsson) |
| 7.2.8.3 |
UE and gNB measurements for NR Positioning |
|
| R1-2003408 |
Discussion on remaining issues on UE and gNB measurements for NR positioning |
vivo |
| R1-2003474 |
Maintenance of UE and gNB measurements for NR positioning |
ZTE |
| R1-2003523 |
Finalizing NR positioning measurements |
Huawei, HiSilicon |
| R1-2003634 |
Remaining issues on NR Positioning Measurements |
CATT |
| R1-2003717 |
Maintenance on measurements for NR Positioning |
Nokia, Nokia Shanghai Bell |
| R1-2003888 |
UE and gNB measurements for NR Positioning |
Samsung |
| R1-2004054 |
Remaining Issues on Measurements for NR Positioning |
OPPO |
| R1-2004471 |
Maintenance on UE and gNB measurements for Positioning |
Qualcomm Incorporated |
| R1-2004645 |
Maintenance of UE and gNB measurements for NR Positioning |
Ericsson |
| R1-2004683 |
FL Summary of Remaining issues on NR Positioning Measurements |
Moderator (CATT) |
| 7.2.8.4 |
Physical-layer procedures to support UE/gNB measurements |
|
| R1-2003409 |
Discussion on remaining issues on physical-layer procedures for NR positioning |
vivo |
| R1-2003475 |
Maintenance of physical-layer procedure for NR positioning |
ZTE |
| R1-2003524 |
Finalizing physical layer procedures for NR positioning |
Huawei, HiSilicon |
| R1-2003635 |
Remaining issues on NR Positioning Procedures |
CATT |
| R1-2003718 |
Maintenance on PHY procedures for NR Positioning |
Nokia, Nokia Shanghai Bell |
| R1-2003810 |
Remaining details on Measurement Procedures |
Futurewei |
| R1-2003889 |
Physical-layer procedures to support UE/gNB measurements |
Samsung |
| R1-2004055 |
Remaining Issues on Physical Layer Procedures for NR Positioning |
OPPO |
| R1-2004136 |
Remaining details of physical-layer procedure to support UE/gNB measurements |
LG Electronics |
| R1-2004472 |
Maintenace on Physical-layer procedures for Positioning |
Qualcomm Incorporated |
| R1-2004646 |
Maintenance of Physical-layer procedures to support UE/gNB measurements |
Ericsson |
| R1-2004662 |
Discussion on remaining opens of physical layer procedures for NR positioning |
Intel Corporation |
| R1-2004720 |
Summary of 7.2.8.4: Physical-layer procedures to support UE/gNB measurements |
Moderator (Qualcomm Incorporated) |
| R1-2004875 |
Summary of Email Discussion [101-e-NR-Pos-03]: Measurements and procedures for NR positioning |
Moderator (Qualcomm Incorporated) |
| R1-2004950 |
[DRAFT] LS on removing SMTC from SSB assistance data |
Huawei |
| R1-2004951 |
LS on removing SMTC from SSB assistance data |
RAN1, Huawei |
| 7.2.8.5 |
Other |
|
| R1-2004056 |
Discussion on RE mapping in reference signal for NR positioning |
OPPO |
| R1-2004608 |
Removal of AP PosSRS feature from Rel-16 |
Huawei, HiSilicon |
| R1-2004647 |
Support of UE Rx-Tx based on Rel15 SRS |
Ericsson |
| 7.2.9 |
Maintenance of NR Mobility Enhancements |
|
| R1-2003747 |
Issue Summary for NR Mobility Enhancements |
Moderator (Intel Corporation) |
| R1-2005092 |
Session notes for 7.2.9 (Maintenance of NR Mobility Enhancements) |
Ad-Hoc Chair (Ericsson) |
| 7.2.9.1 |
Physical Layer Aspects for Mobility Enhancements during HO and SCG Change |
|
| R1-2003330 |
Remaining issues on NR mobility enhancements in physical layer |
ZTE |
| R1-2003506 |
Remaining issues on DAPS-HO |
Huawei, HiSilicon |
| R1-2003676 |
Remaining issues on Physical Layer Aspects for DAPS-HO |
MediaTek Inc. |
| R1-2003748 |
Corrections to Physical layer aspects of NR mobility enhancement |
Intel Corporation |
| R1-2003890 |
Remaining issues for NR Mobility Enhancement |
Samsung |
| R1-2004202 |
Remaining issues on mobility enhancements |
Ericsson |
| R1-2004235 |
On remaining issues on NR mobility enhancements |
Apple |
| R1-2004580 |
Remaining physical layer aspects of dual active protocol stack based HO |
Nokia, Nokia Shanghai Bell |
| R1-2004747 |
Summary of email discussions for [101-e-NR-Mob-Enh-01] |
Moderator (Intel Corporation) |
| R1-2004748 |
Summary of email discussions for [101-e-NR-Mob-Enh-02] |
Moderator (Intel Corporation) |
| R1-2004749 |
Summary of email discussions for [101-e-NR-Mob-Enh-03] |
Moderator (Intel Corporation) |
| R1-2004957 |
Summary#2 of email discussions for [101-e-NR-Mob-Enh-01] |
Moderator (Intel Corporation) |
| R1-2004989 |
Draft CR on correction on PDCCH monitoring for DAPS HO |
Intel Corporation |
| R1-2004990 |
Draft CR on correction on power sharing mode for DAPS HO |
Intel Corporation |
| R1-2004991 |
Draft CR on correction on overlapping uplink transmissions for DAPS HO |
Intel Corporation |
| 7.2.9.2 |
Other |
|
| R1-2003331 |
Discussion on FR2 mobility interruption enhancements |
ZTE |
| R1-2004148 |
Remaining PHY aspects for CHO |
Huawei, HiSilicon |
| 7.2.10 |
Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements (LTE, NR) |
|
| R1-2005093 |
Session notes for 7.2.10 (Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements) |
Ad-Hoc Chair (Ericsson) |
| 7.2.10.1 |
Uplink Power Control for Supporting NR-NR Dual-Connectivity |
|
| R1-2003324 |
Remaining Issues of Dynamic Power Sharing for NR-DC |
ZTE |
| R1-2003410 |
Remaining issues on uplink power control for NR-NR DC |
vivo |
| R1-2003501 |
UL power control for NR-NR dual connectivity |
Huawei, HiSilicon |
| R1-2003672 |
Remaining issues on uplink power control for supporting NR-NR dual-connectivity |
MediaTek Inc. |
| R1-2003749 |
Remaining issues on uplink power control for NN-DC |
Intel Corporation |
| R1-2003891 |
Remaining Issues on UL Power Control for NR-DC |
Samsung |
| R1-2003939 |
Remaining details of Rel-16 DC uplink power control |
Nokia, Nokia Shanghai Bell |
| R1-2004057 |
Text proposals for UL Power Sharing for NR-DC |
OPPO |
| R1-2004236 |
Remaining issues of UL Power Control for NN-DC |
Apple |
| R1-2004237 |
Feature lead summary #1 on UL Power Control for NN-DC |
Moderator (Apple) |
| R1-2004361 |
Remaining issues for NR-DC UL Power Control |
Ericsson |
| R1-2004473 |
Remaining issues on NR-DC power-control |
Qualcomm Incorporated |
| R1-2004710 |
Outcome of preparation discussion on UL Power Control for NN-DC |
Moderator (Apple) |
| R1-2004711 |
Feature lead summary#2 of UL Power Control for NN-DC |
Moderator (Apple) |
| R1-2005017 |
Feature lead summary#3 of UL Power Control for NN-DC |
Moderator (Apple) |
| 7.2.10.2 |
Potential Enhancements to Single Tx Switched Uplink Solution for EN-DC |
|
| R1-2003325 |
Remaining Issues of Single Tx for EN-DC |
ZTE |
| R1-2003502 |
Enhancements for single UL operation for EN-DC |
Huawei, HiSilicon |
| R1-2003673 |
Remaining issues on single Tx switched uplink solution for EN-DC |
MediaTek Inc. |
| R1-2004238 |
Remaining issues on single Tx operation for EN-DC |
Apple |
| R1-2004239 |
Feature lead summary on single Tx operation for EN-DC |
Moderator (Apple) |
| R1-2004362 |
Remaining issues for single Tx UL enhancements |
Ericsson |
| R1-2004901 |
Summary of email discussion [101-e-NR-LTE_NR_DC_CA-SingleTx] |
Moderator (Apple) |
| R1-2004972 |
Summary#2 of email discussion [101-e-NR-LTE_NR_DC_CA-SingleTx] |
Moderator (Apple) |
| 7.2.10.3 |
Support of efficient and low latency serving cell configuration/activation/setup |
|
| R1-2003326 |
Remaining Issues of SCell Dormancy |
ZTE |
| R1-2003411 |
Remaining issues on Scell dormancy like behavior |
vivo |
| R1-2003507 |
Remaining issues on Scell dormancy indication |
Huawei, HiSilicon |
| R1-2003674 |
Remaining issues on SCell dormancy |
MediaTek Inc. |
| R1-2003699 |
Remaining issues for case 2 SCell dormancy indication |
ASUSTeK |
| R1-2003750 |
Remaining issues on SCell dormancy behavior |
Intel Corporation |
| R1-2003892 |
Remaining Issues on Dormancy Scell |
Samsung |
| R1-2004103 |
Discussion on remaing issues of Scell dormancy |
OPPO |
| R1-2004258 |
Remaining issues on Efficient CA design |
Nokia, Nokia Shanghai Bell |
| R1-2004363 |
Remaining issues for reduced latency Scell management for NR CA |
Ericsson |
| R1-2004364 |
Summary of efficient and low latency serving cell configuration/activation/setup |
Moderator (Ericsson) |
| R1-2004474 |
Remaining issues for SCell dormancy |
Qualcomm Incorporated |
| R1-2004717 |
Summary#2 of efficient and low latency serving cell configuration/activation/setup |
Moderator (Ericsson) |
| R1-2005079 |
Summary of email discussion [101-e-NR-LTE_NR_DC_CA-ScellDormancy] |
Moderator(Ericsson) |
| R1-2005080 |
[Draft] LS on SCell Dormancy |
Ericsson |
| R1-2005081 |
LS on SCell Dormancy |
RAN1, Ericsson |
| 7.2.10.4 |
Support of aperiodic CSI-RS triggering with different numerology between CSI-RS and triggering PDCCH |
|
| R1-2003412 |
Remaining issues on aperiodic CSI-RS triggering |
vivo |
| R1-2004058 |
Text proposals for aperiodic CSI-RS triggering with different numerologies |
OPPO |
| R1-2004150 |
Remaining issues on the A-CSI RS triggering with different numerology |
Huawei, HiSilicon |
| R1-2004204 |
Maintenance for cross-carrier CSI-RS triggering |
Ericsson |
| R1-2004475 |
Remaining issues for aperiodic CSI-RS triggering with different numerology |
Qualcomm Incorporated |
| R1-2004638 |
FL summary on aperiodic CSI-RS triggering with different numerology between CSI-RS and triggering PDCCH |
Moderator (Nokia) |
| R1-2004640 |
FL summary #2 on aperiodic CSI-RS triggering with different numerology between CSI-RS and triggering PDCCH |
Moderator (Nokia) |
| 7.2.10.5 |
Support of unaligned frame boundary with slot alignment and partial SFN alignment for R16 NR inter-band CA |
|
| R1-2003327 |
Remaining Issues of Unaligned Frame Boundary CA |
ZTE |
| R1-2003413 |
Remaining issues on unaligned frame boundary for CA |
vivo |
| R1-2003946 |
FL summary on support of unaligned frame boundary for R16 NR inter-band CA |
Moderator (CMCC) |
| R1-2004151 |
Remaining issues on intra-band CA with unaligned frame boundary |
Huawei, HiSilicon |
| R1-2004365 |
Remaining issues for inter-band CA with unaligned frame boundary |
Ericsson |
| R1-2004789 |
Outcome of email discussion of [101-e-NR-LTE_NR_DC_CA-Unaligned_CA] |
Moderator (CMCC) |
| 7.2.10.6 |
Support of cross-carrier scheduling with different numerology |
|
| R1-2003328 |
Remaining Issues on Cross-carrier Scheduling with Mixed Numerologies |
ZTE |
| R1-2003414 |
Remaining issues on cross-carrier scheduling with mix numerologies |
vivo |
| R1-2003508 |
Remaing issues on cross-carrier scheduling with different numerology |
Huawei, HiSilicon |
| R1-2003602 |
Discussion on HARQ-ACK feedback for SPS PDSCH release with cross-carrier scheduling |
CATT |
| R1-2003675 |
Remaining issues on cross-carrier scheduling with different numerology |
MediaTek Inc. |
| R1-2003751 |
Remaining issues on cross-carrier scheduling with different numerology |
Intel Corporation |
| R1-2004037 |
Remaining issue on cross-carrier scheduling with different numerology |
LG Electronics |
| R1-2004366 |
Remaining issues for cross-carrier scheduling with different numerologies |
Ericsson |
| R1-2004639 |
FL summary on cross-carrier scheduling with different numerology |
Moderator (Nokia) |
| R1-2004641 |
FL summary #2 on cross-carrier scheduling with different numerology |
Moderator (Nokia) |
| 7.2.10.7 |
Other |
|
| R1-2003329 |
Discussion on the PUCCH group configuration for NR-DC |
ZTE |
| R1-2004367 |
Data rate handling for intra-FR NR-DC |
Ericsson |
| R1-2004605 |
Discussion on Cross-carrier triggering PDCCH order |
Huawei, HiSilicon |
| 7.2.11 |
NR Rel-16 UE Features |
|
| R1-2004969 |
LS on updated Rel-16 RAN1 UE features lists for NR |
RAN1, NTT DOCOMO, AT&T |
| R1-2004970 |
RAN1 UE features list for Rel-16 NR after RAN1#101-e |
Moderators (AT&T, NTT DOCOMO) |
| R1-2005096 |
LS on updated Rel-16 RAN1 UE features lists for NR |
RAN1, NTT DOCOMO, AT&T |
| R1-2005097 |
RAN1 UE features list for Rel-16 NR after RAN1#101-e |
Moderators (AT&T, NTT DOCOMO) |
| R1-2005105 |
Summary on [101-e-Post-NR-UE-Features-01] |
Moderator (NTT DOCOMO, INC.) |
| R1-2005106 |
Summary on [101-e-Post-NR-UE-Features-02] |
Moderator (NTT DOCOMO, INC.) |
| R1-2005107 |
Summary on [101-e-Post-NR-UE-Features-03] |
Moderator (NTT DOCOMO, INC.) |
| R1-2005108 |
Summary on [101-e-Post-NR-UE-Features-04] |
Moderator (NTT DOCOMO, INC.) |
| R1-2005109 |
LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#101-e |
RAN1, NTT DOCOMO, AT&T |
| R1-2005110 |
RAN1 UE features list for Rel-16 NR updated after RAN1#101-e |
Moderators (AT&T, NTT DOCOMO, INC.) |
| 7.2.11.1 |
UE features for two-step RACH |
|
| R1-2003415 |
Discussion on UE features for 2-step RACH |
vivo |
| R1-2003459 |
Discussion on the remaining issues of the UE features for two-step RACH |
ZTE, Sanechips |
| R1-2003603 |
Discussion of NR Rel-16 UE features for two-step RACH |
CATT |
| R1-2003752 |
Discussion on UE features for two-step RACH |
Intel Corporation |
| R1-2003893 |
UE features for two-step RACH |
Samsung |
| R1-2004137 |
Discussion on UE features for NR 2step RACH |
LG Electronics |
| R1-2004146 |
Rel-16 UE features for 2-step RACH |
Huawei, HiSilicon |
| R1-2004240 |
Views on NR 2-step RACH UE feature |
Apple |
| R1-2004350 |
UE Features for Two-Step RACH |
Ericsson |
| R1-2004400 |
Discussion on UE features for Two-step RACH |
NTT DOCOMO, INC. |
| R1-2004401 |
Summary on UE features for two-step RACH |
Moderator (NTT DOCOMO, INC.) |
| R1-2004476 |
Discussion on two step RACH UE features |
Qualcomm Incorporated |
| R1-2004559 |
On UE features or 2-step RACH |
Nokia, Nokia Shanghai Bell |
| R1-2004814 |
Summary on [101-e-NR-UEFeatures-2step-01] |
Moderator (NTT DOCOMO, INC.) |
| R1-2004815 |
Summary on [101-e-NR-UEFeatures-2step-02] |
Moderator (NTT DOCOMO, INC.) |
| 7.2.11.2 |
UE features for NR-U |
|
| R1-2003416 |
Discussion on UE features for NRU |
vivo |
| R1-2003460 |
Discussion on the remaining issues of the UE features for NR-U |
ZTE, Sanechips |
| R1-2003694 |
Views on Rel-16 UE features for NR-U |
MediaTek Inc. |
| R1-2003848 |
UE features for NR-U |
Ericsson |
| R1-2003894 |
UE features for NR-U |
Samsung |
| R1-2004019 |
Discussion on UE features for NR-U |
LG Electronics |
| R1-2004091 |
Discussion on UE feature for NRU |
OPPO |
| R1-2004152 |
Rel-16 UE features for NR-U |
Huawei, HiSilicon |
| R1-2004241 |
Discussions on NR-U UE features |
Apple |
| R1-2004402 |
UE features for NR-U |
NTT DOCOMO, INC |
| R1-2004403 |
Summary on UE features for NR-U |
Moderator (NTT DOCOMO, INC.) |
| R1-2004477 |
Discussion on NR-U UE features |
Qualcomm Incorporated |
| R1-2004560 |
On UE features NR Unlicensed |
Nokia, Nokia Shanghai Bell |
| R1-2004816 |
Summary on [101-e-NR-UEFeatures-NRU-01] |
Moderator (NTT DOCOMO, INC.) |
| R1-2004817 |
Summary on [101-e-NR-UEFeatures-NRU-02] |
Moderator (NTT DOCOMO, INC.) |
| R1-2004818 |
Summary on [101-e-NR-UEFeatures-NRU-03] |
Moderator (NTT DOCOMO, INC.) |
| R1-2004965 |
LS on UE capability on wideband carrier operation for NR-U |
RAN1, MediaTek |
| 7.2.11.3 |
UE features for IAB |
|
| R1-2003545 |
Discussion on NR Rel-16 IAB MT features |
ZTE, Sanechips |
| R1-2003753 |
UE features for IAB |
Intel Corporation |
| R1-2003895 |
UE features for IAB |
Samsung |
| R1-2004138 |
Discussion on UE features for NR IAB |
LG Electronics |
| R1-2004147 |
Rel-16 UE features for IAB |
Huawei, HiSilicon |
| R1-2004282 |
Support of Rel-15 UE features by IAB-MTs |
AT&T |
| R1-2004283 |
Summary of UE features for IAB |
Moderator (AT&T) |
| R1-2004561 |
On UE features for IAB |
Nokia, Nokia Shanghai Bell |
| R1-2004585 |
UE features for IAB-MTs |
Ericsson |
| R1-2004953 |
[DRAFT] Reply LS on RAN4 IAB-MT feature list agreement |
Qualcomm |
| R1-2004954 |
Reply LS on RAN4 IAB-MT feature list agreement |
RAN1, Qualcomm |
| R1-2005025 |
Summary of email discussion/approval [101-e-NR-IAB-UEFeatures-01] |
Moderator (AT&T) |
| R1-2005026 |
Summary of email discussion/approval [101-e-NR-IAB-UEFeatures-02] |
Moderator (AT&T) |
| R1-2005027 |
Summary of email discussion/approval [101-e-NR-IAB-UEFeatures-03] |
Moderator (AT&T) |
| 7.2.11.4 |
UE features for 5G V2X |
|
| R1-2003417 |
Discussion on 5G V2X UE features |
vivo |
| R1-2003570 |
Discussion on Rel-16 NR UE features for 5G V2X |
LG Electronics |
| R1-2003576 |
Views on UE features for 5G V2X |
ZTE, Sanechips |
| R1-2003605 |
Discussion of UE features for NR V2X |
CATT |
| R1-2003696 |
Views on Rel-16 UE features for NR V2X |
MediaTek Inc. |
| R1-2003754 |
On UE features for NR V2X |
Intel Corporation |
| R1-2003809 |
Remaining details of features for Rel-16 V2X |
Futurewei |
| R1-2003896 |
UE features for NR V2X |
Samsung |
| R1-2004080 |
Discussion on UE feature list for Release16 5G-V2X |
OPPO |
| R1-2004143 |
Rel-16 UE features for 5G V2X |
Huawei, HiSilicon |
| R1-2004242 |
Discussions on UE Features on V2X |
Apple |
| R1-2004284 |
Summary of UE features for 5G V2X |
Moderator (AT&T) |
| R1-2004404 |
UE features for 5G V2X |
NTT DOCOMO, INC. |
| R1-2004479 |
Discussion on V2X UE features |
Qualcomm Incorporated |
| R1-2004553 |
UE features for 5G V2X |
Ericsson |
| R1-2004562 |
On UE features for 5G V2X |
Nokia, Nokia Shanghai Bell |
| R1-2004576 |
UE features for 5G V2X |
Ericsson |
| R1-2005022 |
Session Notes of AI 7.2.11.4 |
Ad-Hoc Chair (AT&T) |
| R1-2005028 |
Summary of email discussion/approval [101-e-NR-5G_V2X_NRSL-UEFeatures-01] |
Moderator (AT&T) |
| R1-2005029 |
Summary of email discussion/approval [101-e-NR-5G_V2X_NRSL-UEFeatures-02] |
Moderator (AT&T) |
| R1-2005030 |
Summary of email discussion/approval [101-e-NR-5G_V2X_NRSL-UEFeatures-03] |
Moderator (AT&T) |
| R1-2005031 |
Summary of email discussion/approval [101-e-NR-5G_V2X_NRSL-UEFeatures-04] |
Moderator (AT&T) |
| R1-2005032 |
Summary of email discussion/approval [101-e-NR-5G_V2X_NRSL-UEFeatures-05] |
Moderator (AT&T) |
| R1-2005111 |
Summary of email discussion/approval [101-e-Post-NR-UE-Features-05] |
Moderator (AT&T) |
| 7.2.11.5 |
UE features for URLLC/IIoT |
|
| R1-2003316 |
UE features for URLLC |
China Unicom |
| R1-2003333 |
Discussion on UE feature for URLLC/IIoT |
ZTE |
| R1-2003418 |
Discussion on URLLC/IIOT UE features |
vivo |
| R1-2003446 |
On UE Features for URLLC and IIoT |
Ericsson |
| R1-2003606 |
Discussion of UE features for NR URLLC/IIoT |
CATT |
| R1-2003695 |
Views on Rel-16 UE features for NR URLLC/IIoT |
MediaTek Inc. |
| R1-2003755 |
On UE features for Rel-16 eURLLC and IIoT |
Intel Corporation |
| R1-2003897 |
UE features for URLLC/IIoT |
Samsung |
| R1-2004036 |
Discussion on UE features for URLLC/IIoT |
LG Electronics |
| R1-2004122 |
Discussion on UE features for URLLC/IIoT |
OPPO |
| R1-2004157 |
Rel-16 UE features for URLLC |
Huawei, HiSilicon |
| R1-2004243 |
Discussions on UE Features for URLLC/IIoT |
Apple |
| R1-2004405 |
Rel-16 UE features for URLLC/IIoT |
NTT DOCOMO, INC |
| R1-2004406 |
Summary on UE features for URLLC/IIoT |
Moderator (NTT DOCOMO, INC.) |
| R1-2004480 |
Discussion on eURLLC and IIOT UE features |
Qualcomm Incorporated |
| R1-2004563 |
On UE features for URLLC/IIOT |
Nokia, Nokia Shanghai Bell |
| R1-2004733 |
Discussion on eURLLC and IIOT UE features |
Qualcomm Incorporated |
| R1-2004819 |
Summary on [101-e-NR-UEFeatures-URLLCIIoT-01] |
Moderator (NTT DOCOMO, INC.) |
| R1-2004820 |
Summary on [101-e-NR-UEFeatures-URLLCIIoT-02] |
Moderator (NTT DOCOMO, INC.) |
| 7.2.11.6 |
UE features for eMIMO |
|
| R1-2003346 |
UE features for eMIMO |
China Unicom |
| R1-2003419 |
Further discussion on eMIMO UE features |
vivo |
| R1-2003476 |
NR eMIMO UE features |
ZTE |
| R1-2003607 |
Discussion on Rel.16 MIMO UE features |
CATT |
| R1-2003690 |
Views on Rel-16 UE features for NR eMIMO |
MediaTek Inc. |
| R1-2003756 |
UE features for NR eMIMO |
Intel Corporation |
| R1-2003898 |
On UE features for eMIMO |
Samsung |
| R1-2003933 |
Discussion on RAN1 UE feature for NR eMIMO |
LG Electronics |
| R1-2003960 |
Discussion on Rel-16 eMIMO UE features |
CMCC |
| R1-2003983 |
Discussion on UE features for eMIMO |
Spreadtrum Communications |
| R1-2004059 |
Discussion on Rel-16 eMIMO UE features |
OPPO |
| R1-2004159 |
Rel-16 UE features for MIMO |
Huawei, HiSilicon |
| R1-2004244 |
Views on Rel-16 eMIMO UE feature list |
Apple |
| R1-2004285 |
Summary of UE features for eMIMO |
Moderator (AT&T) |
| R1-2004351 |
UE Features for eMIMO |
Ericsson |
| R1-2004481 |
Discussion on eMIMO UE features |
Qualcomm Incorporated |
| R1-2004556 |
Discussion on UE features for eMIMO |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2004564 |
On UE features for eMIMO |
Nokia, Nokia Shanghai Bell |
| R1-2004668 |
Discussion on eMIMO UE features |
Qualcomm Incorporated |
| R1-2005023 |
Session Notes of AI 7.2.11.6 |
Ad-Hoc Chair (AT&T) |
| R1-2005033 |
Summary of email discussion/approval [101-e-NR-eMIMO-UEFeature-01] |
Moderator (AT&T) |
| R1-2005034 |
Summary of email discussion/approval [101-e-NR-eMIMO-UEFeature-02] |
Moderator (AT&T) |
| R1-2005035 |
Summary of email discussion/approval [101-e-NR-eMIMO-UEFeature-03] |
Moderator (AT&T) |
| R1-2005036 |
Summary of email discussion/approval [101-e-NR-eMIMO-UEFeature-04] |
Moderator (AT&T) |
| R1-2005113 |
Summary of email discussion/approval [101-e-Post-NR-UE-Features-07] |
Moderator (AT&T) |
| 7.2.11.7 |
UE features for UE power savings |
|
| R1-2003420 |
Discussion on UE features for power saving |
vivo |
| R1-2003490 |
Discussion on UE feature for UE power saving |
ZTE |
| R1-2003608 |
Discussion on Rel-16 UE power saving feature |
CATT |
| R1-2003666 |
Views on Rel-16 UE features for NR UE power savings |
MediaTek Inc. |
| R1-2003757 |
On UE features for Rel-16 UE Power Saving |
Intel Corporation |
| R1-2004112 |
Discussion on Power Saving related UE features |
OPPO |
| R1-2004153 |
Rel-16 UE features for UE power saving |
Huawei, HiSilicon |
| R1-2004286 |
Summary of UE features for UE power savings |
Moderator (AT&T) |
| R1-2004368 |
Discussion on UE features for UEPS |
Ericsson |
| R1-2004407 |
Discussion on UE features for UE power saving |
NTT DOCOMO, INC. |
| R1-2004482 |
Discussion on power saving UE features |
Qualcomm Incorporated |
| R1-2004538 |
UE features for UE power saving |
Panasonic Corporation |
| R1-2004565 |
On UE features for UE Power Savings |
Nokia, Nokia Shanghai Bell |
| R1-2005037 |
Summary of email discussion/approval [101-e-NR- UE_pow_sav-UEFeatures-01] |
Moderator (AT&T) |
| R1-2005038 |
Summary of email discussion/approval [101-e-NR- UE_pow_sav-UEFeatures-02] |
Moderator (AT&T) |
| R1-2005039 |
Summary of email discussion/approval [101-e-NR- UE_pow_sav-UEFeatures-03] |
Moderator (AT&T) |
| 7.2.11.8 |
UE features for NR positioning |
|
| R1-2003421 |
Discussion on UE features for NR positioning |
vivo |
| R1-2003477 |
NR positioning UE features |
ZTE |
| R1-2003609 |
Discussion of UE features for NR positioning |
CATT |
| R1-2003693 |
Views on Rel-16 UE features for NR positioning |
MediaTek Inc. |
| R1-2003758 |
On UE features for NR positioning |
Intel Corporation |
| R1-2003899 |
UE features for NR positioning |
Samsung |
| R1-2004060 |
Discussion on UE features for NR Positioning |
OPPO |
| R1-2004139 |
Discussion on UE features for NR positioning |
LG Electronics |
| R1-2004154 |
Rel-16 UE features for NR positioning |
Huawei, HiSilicon |
| R1-2004408 |
Summary on UE features for NR positioning |
Moderator (NTT DOCOMO, INC.) |
| R1-2004483 |
Discussion on NR Positioning UE features |
Qualcomm Incorporated |
| R1-2004566 |
On UE features for NR Positioning |
Nokia, Nokia Shanghai Bell |
| R1-2004648 |
View on UE features for NR positioning |
Ericsson |
| R1-2004821 |
Summary on [101-e-NR-UEFeatures-Positioning-01] |
Moderator (NTT DOCOMO, INC.) |
| R1-2004822 |
Summary on [101-e-NR-UEFeatures-Positioning-02] |
Moderator (NTT DOCOMO, INC.) |
| 7.2.11.9 |
UE features for NR mobility enhancements |
|
| R1-2003334 |
Discussion on UE feature for NR mobility enhancements |
ZTE |
| R1-2003678 |
Views on Rel-16 UE features for NR mobility enhancements |
MediaTek Inc. |
| R1-2003759 |
UE feature for NR Mobility Enhancement |
Intel Corporation |
| R1-2003900 |
UE features for NR mobility enhancement |
Samsung |
| R1-2004149 |
Rel-16 UE features for mobility enhancement |
Huawei, HiSilicon |
| R1-2004203 |
UE features for mobility enhancements |
Ericsson |
| R1-2004245 |
Views on NR mobility ehancement UE feature |
Apple |
| R1-2004287 |
Summary of UE features for NR mobility enhancements |
Moderator (AT&T) |
| R1-2004484 |
Discussion on Mobility Enhancements UE features |
Qualcomm Incorporated |
| R1-2004567 |
On UE features for NR Mobility Enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2005040 |
Summary of email discussion/approval [101-e-NR-Mob_enh-UEFeatures-01] |
Moderator (AT&T) |
| R1-2005041 |
Summary of email discussion/approval [101-e-NR-Mob_enh-UEFeatures-02] |
Moderator (AT&T) |
| R1-2005042 |
Summary of email discussion/approval [101-e-NR-Mob_enh-UEFeatures-03] |
Moderator (AT&T) |
| R1-2005043 |
Summary of email discussion/approval [101-e-NR-Mob_enh-UEFeatures-04] |
Moderator (AT&T) |
| 7.2.11.10 |
UE features for MR-DC/CA |
|
| R1-2003335 |
Discussion on UE feature for MR-DC |
ZTE |
| R1-2003677 |
Views on Rel-16 UE features for MR-DC/CA |
MediaTek Inc. |
| R1-2003760 |
UE feature for MR-DC |
Intel Corporation |
| R1-2003901 |
UE features for MR-DC/CA |
Samsung |
| R1-2004144 |
Rel-16 UE features for MR-DC/CA |
Huawei, HiSilicon |
| R1-2004369 |
Discussion on UE features for MR-DC |
Ericsson |
| R1-2004409 |
Discussion on UE features for MR-DC/CA enhancement |
NTT DOCOMO, INC. |
| R1-2004410 |
Summary on UE features for MR-DC/CA |
Moderator (NTT DOCOMO, INC.) |
| R1-2004478 |
Discussion on UE features for MR-DC/CA |
Qualcomm Incorporated |
| R1-2004485 |
Discussion on UE features for MR-DC/CA |
Qualcomm Incorporated |
| R1-2004568 |
On UE features for MR-DC/CA |
Nokia, Nokia Shanghai Bell |
| R1-2004823 |
Summary on [101-e-NR-UEFeatures-MRDCCA-01] |
Moderator (NTT DOCOMO, INC.) |
| R1-2004824 |
Summary on [101-e-NR-UEFeatures-MRDCCA-02] |
Moderator (NTT DOCOMO, INC.) |
| 7.2.11.11 |
UE features for CLI/RIM |
|
| R1-2003491 |
Discussion on UE feature for CLI |
ZTE |
| R1-2004140 |
Discussion on UE features for NR CLIRIM |
LG Electronics |
| R1-2004145 |
Rel-16 UE features for CLI/RIM |
Huawei, HiSilicon |
| R1-2004411 |
Discussion on UE features for CLI/RIM |
NTT DOCOMO, INC. |
| R1-2004412 |
Summary on UE features for CLI/RIM |
Moderator (NTT DOCOMO, INC.) |
| R1-2004486 |
Discussion on UE features for CLI |
Qualcomm Incorporated |
| R1-2004587 |
UE features for CLI/RIM |
Ericsson |
| R1-2004825 |
Summary on [101-e-NR-UEFeatures-CLIRIM-01] |
Moderator (NTT DOCOMO, INC.) |
| 7.2.11.12 |
UE features for TEIs |
|
| R1-2003422 |
Discussion on UE features for TEI 14-7 |
vivo |
| R1-2003478 |
NR TEI UE features |
ZTE |
| R1-2003604 |
Discussion on UE features for TEI |
CATT |
| R1-2003691 |
Views on Rel-16 UE features for NR TEIs |
MediaTek Inc. |
| R1-2003761 |
UE features for NR TEI |
Intel Corporation |
| R1-2004061 |
Discussion on Rel-16 UE features for TEIs |
OPPO |
| R1-2004161 |
Discussion on Rel-16 UE features for TEIs |
Huawei, HiSilicon |
| R1-2004177 |
Remaining issues of UE features for TEIs |
Ericsson |
| R1-2004413 |
Discussion on UE features for NR TEI |
NTT DOCOMO, INC. |
| R1-2004414 |
Summary on UE features for TEIs |
Moderator (NTT DOCOMO, INC.) |
| R1-2004487 |
Discussion on UE features for TEIs |
Qualcomm Incorporated |
| R1-2004569 |
On UE features for TEIs |
Nokia, Nokia Shanghai Bell |
| R1-2004826 |
Summary on [101-e-NR-UEFeatures-TEIs-01] |
Moderator (NTT DOCOMO, INC.) |
| R1-2004827 |
Summary on [101-e-NR-UEFeatures-TEIs-02] |
Moderator (NTT DOCOMO, INC.) |
| 7.2.11.13 |
Other |
|
| R1-2003336 |
Remaining issues on Rel-16 NR UE features |
ZTE |
| R1-2003762 |
Rel-16 UE feature - Others |
Intel Corporation |
| R1-2003902 |
UE features for other aspects |
Samsung |
| R1-2004062 |
Discussion on the support of SRS transmission in all symbols of a slot |
OPPO |
| R1-2004415 |
Summary on NR UE features for others |
Moderator (NTT DOCOMO, INC.) |
| R1-2004488 |
Discussion on UE features for Others |
Qualcomm Incorporated |
| R1-2004586 |
General discussion on NR Rel-16 UE features |
Ericsson |
| R1-2004628 |
Other aspects of Rel-16 NR UE features |
Huawei, HiSilicon |
| R1-2004682 |
General discussion on NR Rel-16 UE features |
Ericsson |
| R1-2004732 |
Discussion on UE features for Others |
Qualcomm Incorporated |
| R1-2004828 |
Summary on [101-e-NR-UEFeatures-Others-01] |
Moderator (NTT DOCOMO, INC.) |
| 7.2.12 |
Other |
|
| R1-2003423 |
Remaining issues on Half-Duplex Operation in CA |
vivo |
| R1-2003492 |
Remaining issues on CLI |
ZTE |
| R1-2003610 |
Remaining issues of half-duplex operation in CA |
CATT |
| R1-2003692 |
On TRS muting for NR coexistence with a narrow band system |
MediaTek Inc. |
| R1-2003763 |
Maintenance of aperiodic CSI-RS triggering with beam switching timing of 224 and 336 |
Intel Corporation |
| R1-2003923 |
On ambiguous TBS due to ambiguity of Ninfo |
NEC |
| R1-2004259 |
On remaining issues of HD UE feature |
Nokia, Nokia Shanghai Bell |
| R1-2004416 |
Summary on Rel-16 NR TEI related discussion |
Moderator (NTT DOCOMO, INC.) |
| R1-2004604 |
Discussion on the conditions of rate matching pattern overlapping with PDSCH DMRS symbols |
Huawei, HiSilicon |
| R1-2004642 |
Remaining issue for Rel-16 maintenance |
Ericsson |
| R1-2004829 |
Summary on [101-e-NR-TEIs-01] |
Moderator (NTT DOCOMO, INC.) |
| R1-2004830 |
Summary on [101-e-NR-TEIs-02] |
Moderator (NTT DOCOMO, INC.) |
| R1-2004831 |
Summary on [101-e-NR-TEIs-03] |
Moderator (NTT DOCOMO, INC.) |
| 8.1 |
Study on supporting NR from 52.6GHz to 71 GHz |
|
| R1-2004703 |
Summary of discussions on supporting NR from 52.6 GHz to 71 GHz |
Moderator (Intel Corporation) |
| R1-2004751 |
Skeleton TR 38.808-001: Study on supporting NR from 52.6 GHz to 71 GHz |
Intel Corporation |
| R1-2004754 |
Summary of email discussions for [101-e-NR-52_71_GHz] |
Moderator (Intel Corporation) |
| R1-2005003 |
Summary#2 of email discussions for [101-e-NR-52_71_GHz] |
Moderator (Intel Corporation) |
| R1-2005094 |
Session notes for 8.1 (Study on supporting NR from 52.6 GHz to 71 GHz) |
Ad-Hoc Chair (Ericsson) |
| R1-2005185 |
Summary of email discussions for [101-e-Post-NR-52_71_GHz] |
Moderator (Intel Corporation) |
| R1-2005186 |
Summary#2 of email discussions for [101-e-Post-NR-52_71_GHz] |
Moderator (Intel Corporation) |
| R1-2005191 |
[Draft] LS to RAN4 on Phase noise and other RF Impairment modelling |
Ericsson |
| R1-2005193 |
Summary#3 of email discussions for [101-e-Post-NR-52_71_GHz] |
Moderator (Intel Corporation) |
| R1-2005194 |
Skeleton TR 38.808-001: Study on supporting NR from 52.6 GHz to 71 GHz |
Intel Corporation |
| R1-2005195 |
[Draft] LS to RAN4 on Phase noise and other RF Impairment modelling |
Ericsson |
| R1-2005196 |
LS to RAN4 on Phase noise and other RF Impairment modelling |
RAN1, Ericsson |
| R1-2005197 |
Session notes post-RAN1#101-e for 8.1 (Study on supporting NR from 52.6 GHz to 71 GHz) |
Ad-Hoc Chair (Ericsson) |
| 8.1.1 |
Required changes to NR using existing DL/UL NR waveform |
|
| R1-2003286 |
Channelization in unlicensed spectrum above 52.6GHz and below 71GHz |
Futurewei |
| R1-2003293 |
Link level evaluation methodology and considerations for PHY design in 52.6-71 GHz using NR waveform |
Huawei, HiSilicon |
| R1-2003304 |
Discussion on potential physical layer impacts for NR beyond 52.6 GHz |
Lenovo, Motorola Mobility |
| R1-2003424 |
Discussion on requried changes to NR using existing DL/UL NR waveform |
vivo |
| R1-2003461 |
Discussion on the required changes to NR for above 52.6GHz |
ZTE, Sanechips |
| R1-2003636 |
System Analysis and evaluation methodology of NR opration up to 71 GHz |
CATT |
| R1-2003679 |
On Required changes to NR using existing DL/UL NR waveform for supporting NR from 52.6GHz to 71 GHz |
MediaTek Inc. |
| R1-2003764 |
Discussion on Required Changes to NR in 52.6 – 71 GHz |
Intel Corporation |
| R1-2003777 |
Waveform Enhancements for 60GHz operation |
Charter Communications, Inc |
| R1-2003811 |
Required changes to NR using existing DL/UL NR waveform |
Nokia, Nokia Shanghai Bell |
| R1-2003849 |
On NR operations in 52.6 to 71 GHz |
Ericsson |
| R1-2003903 |
Design aspects for extending NR to up to 71 GHz |
Samsung |
| R1-2003945 |
Discussions on Changes to NR Using Existing DL/UL NR Waveform |
Quectel |
| R1-2003961 |
Discussion on required changes to NR for above 52.6GHz |
CMCC |
| R1-2004004 |
Discussion on required changes to NR using existing NR waveform |
Spreadtrum Communications |
| R1-2004038 |
Consideration on required physical layer changes to support NR above 52.6 GHz |
LG Electronics |
| R1-2004096 |
Discussion on the waveform for DL/UL at above 52.6 GHz |
OPPO |
| R1-2004188 |
Considerations on bandwidth and subcarrier spacing for above 52.6 GHz |
Sony |
| R1-2004247 |
On Required changes to NR using existing DL/UL NR Waveform |
Apple |
| R1-2004299 |
Consideration on supporting above 52.6GHz in NR |
InterDigital, Inc. |
| R1-2004301 |
Consideration on required changes to NR using existing NR waveform |
Fujitsu |
| R1-2004312 |
Study on the required changes to NR using existing DL/UL NR waveform |
NEC |
| R1-2004333 |
Initial views of required changes of NR DL/UL waveform |
Sharp |
| R1-2004340 |
Discussion on required changes to NR using existing DL/UL waveform |
ITRI |
| R1-2004417 |
Evaluation Methodology and Required Changes on NR on 52.6 to 71 GHz |
NTT DOCOMO, INC. |
| R1-2004500 |
NR using existing DL-UL NR waveform to support operation between 52p6 GHz and 71 GHz |
Qualcomm Incorporated |
| R1-2004519 |
Discussions on required changes on supporting NR from 52.6GHz to 71 GHz |
CAICT |
| R1-2004593 |
On NR operation between 52.6 GHz and 71 GHz |
Convida Wireless |
| 8.1.2 |
Channel access mechanism |
|
| R1-2003287 |
Considerations on channel access in the unlicensed spectrum above 52.6GHz and below 71GHz |
Futurewei |
| R1-2003294 |
Channel access mechanism for 60 GHz unlicensed operation |
Huawei, HiSilicon |
| R1-2003305 |
Discussion on channel access for NR beyond 52.6 GHz |
Lenovo, Motorola Mobility |
| R1-2003425 |
Discussion on channel access mechanism |
vivo |
| R1-2003462 |
Discussion on the channel access mechanism for above 52.6GHz |
ZTE, Sanechips |
| R1-2003637 |
Channel Access Mechanism in support |
CATT |
| R1-2003680 |
On channel access mechanism from 52.6GHz to 71GHz |
MediaTek Inc. |
| R1-2003765 |
Channel Access Procedure for NR in 52.6 - 71 GHz |
Intel Corporation |
| R1-2003780 |
Channel access mechanisms for 60 GHz NR-U |
Charter Communications, Inc |
| R1-2003812 |
NR coexistence mechanisms for 60 GHz unlicensed band |
Nokia, Nokia Shanghai Bell |
| R1-2003850 |
Channel Access Mechanism |
Ericsson |
| R1-2003904 |
Channel access mechanism for 60 GHz unlicensed spectrum |
Samsung |
| R1-2003921 |
Discussion on channel access mechanism for supporting NR from 52.6GHz to 71 GHz |
Beijing Xiaomi Mobile Software |
| R1-2003962 |
Discussion on channel access for above 52.6GHz |
CMCC |
| R1-2004005 |
Discussion on channel access mechanism for above 52.6GHz |
Spreadtrum Communications |
| R1-2004039 |
Considerations on channel access mechanism to support NR above 52.6 GHz |
LG Electronics |
| R1-2004097 |
Discussion on channel access mechanism for above 52.6GHz |
OPPO |
| R1-2004174 |
Channel access mechanism |
TCL Communication Ltd. |
| R1-2004189 |
Channel access mechanism for 60 GHz unlicensed spectrum |
Sony |
| R1-2004248 |
On Unlicensed Channel Access Mechanisms for > 52.6GHz |
Apple |
| R1-2004288 |
Channel access mechanisms for NR from 52.6-71GHz |
AT&T |
| R1-2004300 |
On Channel Access Mechanisms |
InterDigital, Inc. |
| R1-2004303 |
Discussions on channel access mechanism for NR from 52.6GHz to 71 GHz |
Quectel |
| R1-2004313 |
Study on the channel access mechanism |
NEC |
| R1-2004334 |
Channel access mechanism |
Sharp |
| R1-2004341 |
Discussion on channel access mechanism |
ITRI |
| R1-2004418 |
Channel Access Mechanism for NR in 60 GHz unlicensed spectrum |
NTT DOCOMO, INC. |
| R1-2004489 |
Channel access mechanism for NR in 52.6 to 71GHz band |
Qualcomm Incorporated |
| R1-2004520 |
Discussions on channel access mechanism on supporting NR from 52.6GHz to 71 GHz |
CAICT |
| R1-2004558 |
Discussion on channel access for unlicensed spectrum from 52.6GHz to 71 GHz |
Potevio |
| R1-2004594 |
Considerations on channel access mechanism for NR supporting from 52.6 to 71 GHz |
Convida Wireless |
| 8.1.3 |
Other |
|
| R1-2003426 |
Evaluation on different numerologies for NR using existing DL/UL NR waveform |
vivo |
| R1-2003463 |
Discussion on the evaluation assumptions for above 52.6GHz |
ZTE, Sanechips |
| R1-2003766 |
Considerations on performance evaluation for NR in 52.6-71GHz |
Intel Corporation |
| R1-2003813 |
Performance of existing DL NR waveform beyond 52.6 GHz |
Nokia, Nokia Shanghai Bell |
| R1-2003851 |
Enhanced phase noise modeling |
Ericsson |
| R1-2003905 |
Evaluaton assumptions for SLS and LLS |
Samsung |
| R1-2004040 |
Consideration on multi-carrier operation for NR above 52.6 GHz |
LG Electronics |
| R1-2004098 |
Discussion on deployment scenarios for carrier frequency above 52.6GHz |
OPPO |
| R1-2004419 |
Potential Enhancements for NR on 52.6 to 71 GHz |
NTT DOCOMO, INC. |
| R1-2004606 |
System level evaluation methodology and results for 60 GHz unlicensed operation |
Huawei, HiSilicon |
| 8.2 |
Study on NR Positioning Enhancements |
|
| R1-2003638 |
Work plan for Study on NR Positioning Enhancements |
CATT, Intel, Ericsson |
| R1-2004649 |
TR skeleton for TR 38.857: Study on NR Positioning Enhancements |
Ericsson |
| R1-2004701 |
FL Summary of Study on NR Positioning Enhancements |
Moderator (CATT) |
| R1-2004868 |
FL Summary#2 of Study on NR Positioning Enhancements |
Moderator (CATT) |
| R1-2004948 |
TR skeleton for TR 38.857: Study on NR Positioning Enhancements |
Ericsson |
| R1-2004961 |
FL Summary#3 of Study on NR Positioning Enhancements |
Moderator (CATT) |
| R1-2005049 |
FL Summary#4 of Study on NR Positioning Enhancements |
Moderator (CATT) |
| R1-2005095 |
Session notes for 8.2 (Study on NR positioning enhancements) |
Ad-Hoc Chair (Ericsson) |
| R1-2005102 |
Summary of Email Discussion [101-e-Post-NR-Pos-Enh] |
Moderator (CATT) |
| R1-2005188 |
Summary#2 of Email Discussion [101-e-Post-NR-Pos-Enh] |
Moderator (CATT) |
| R1-2005198 |
Session notes post-RAN1#101-e for 8.2 (Study on NR positioning enhancements) |
Ad-Hoc Chair (Ericsson) |
| 8.2.1 |
Additional scenarios for evaluation |
|
| R1-2003284 |
IIOT Scenarios for Positioning |
Futurewei |
| R1-2003295 |
Discussion on scenarios and evaluation methodology for Rel-17 positioning |
Huawei, HiSilicon |
| R1-2003427 |
Discussion on additional scenarios for NR positioning evaluation |
vivo |
| R1-2003479 |
Additional scenarios for evaluation on positioning enhancements |
ZTE |
| R1-2003639 |
Summary of discussion on IIoT Scenarios for NR Positioning Enhancements (prior to the meeting) |
Moderator (CATT) |
| R1-2003640 |
IIoT use cases and scenarios for evaluation of NR Positioning Enhancements |
CATT |
| R1-2003719 |
Additional scenarios for evaluation of NR positioning |
Nokia, Nokia Shanghai Bell |
| R1-2003767 |
I-IoT scenarios for NR positioning evaluations |
Intel Corporation |
| R1-2003906 |
Additional scenarios for evaluation |
Samsung |
| R1-2003963 |
Discussions on IIoT scenarios for positioning |
CMCC |
| R1-2004063 |
Discussion on Scenarios for Evaluation |
OPPO |
| R1-2004141 |
Discussion on additional scenarios for evaluation |
LG Electronics |
| R1-2004190 |
Considerations on Scenarios for Evaluations of IIoT Positioning |
Sony |
| R1-2004199 |
View on scenarios and evaluation parameters for Rel 17 positioning enhancement |
CEWiT |
| R1-2004490 |
Considerations on Additional Scenarios for Evaluation |
Qualcomm Incorporated |
| R1-2004517 |
Additional scenarios and considerations for NR positioning |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2004650 |
Additional scenarios for performance evaluations |
Ericsson |
| 8.2.2 |
Evaluation of achievable positioning accuracy and latency |
|
| R1-2003296 |
Performance evaluation for Rel-17 positioning |
Huawei, HiSilicon |
| R1-2003428 |
Evaluation of achievable accuracy and latency for NR positioning enhancements |
vivo |
| R1-2003480 |
Evaluation results of additional scenarios for positioning |
ZTE |
| R1-2003547 |
Evaluation of Rel-16 Positioning for IIOT |
Futurewei |
| R1-2003641 |
Discussion of evaluation of NR positioning performance |
CATT |
| R1-2003668 |
Evaluation of DL-AoD technique under IIOT scenario |
MediaTek Inc. |
| R1-2003720 |
Views on evaluation of achievable positioning accuracy and latency |
Nokia, Nokia Shanghai Bell |
| R1-2003768 |
Initial analysis of NR positioning performance in I-IoT scenarios |
Intel Corporation |
| R1-2003907 |
Evaluation of achievable positioning accuracy and latency |
Samsung |
| R1-2003964 |
Discussions on evaluation methodology of latency |
CMCC |
| R1-2004064 |
Evaluation of NR positioning in IIOT scenario |
OPPO |
| R1-2004191 |
Considerations on Evaluation of Positioning Accuracy and Latency |
Sony |
| R1-2004491 |
Initial Evaluation of achievable Positioning Accuracy & Latency |
Qualcomm Incorporated |
| R1-2004518 |
Evaluation of positioning enhancements |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2004651 |
Evaluation of Achievable Positioning Accuracy and Latency |
Ericsson |
| R1-2004725 |
Initial analysis of NR positioning performance in I-IoT scenarios |
Intel Corporation |
| 8.2.3 |
Potential positioning enhancements |
|
| R1-2003285 |
IIOT Positioning techniques Consideration |
Futurewei |
| R1-2003297 |
Discussion of positioning enhancement |
Huawei, HiSilicon |
| R1-2003429 |
Discussion on potential positioning enhancements |
vivo |
| R1-2003481 |
Potential NR positioning enhancements for Rel.17 |
ZTE |
| R1-2003642 |
Discussion of NR positioning enhancements |
CATT |
| R1-2003669 |
Views on Positioning enhancement for Rel-17 |
MediaTek Inc. |
| R1-2003701 |
Potential positioning enhancements |
BUPT |
| R1-2003721 |
Initial views on potential positioning enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2003769 |
Potential NR positioning enhancements |
Intel Corporation |
| R1-2003908 |
Potential positioning enhancements |
Samsung |
| R1-2003965 |
Discussions on potential positioning enhancements |
CMCC |
| R1-2003977 |
Positioning enhancements for RRC IDLE and RRC INACTIVE state UE |
Beijing Xiaomi Mobile Software |
| R1-2003988 |
Discussion on potential positioning enhancements |
Spreadtrum Communications |
| R1-2004065 |
Discussions on NR Positioning Enhancements |
OPPO |
| R1-2004142 |
Discussion on potential positioning enhancements |
LG Electronics |
| R1-2004175 |
On Potential Rel-17 NR Positioning Enhancements |
Lenovo, Motorola Mobility |
| R1-2004192 |
Potential Techniques for Positioning Enhancements |
Sony |
| R1-2004420 |
Discussion on potential techniques for NR Positioning Enhancements |
NTT DOCOMO, INC. |
| R1-2004492 |
Initial thoughts on Potential Positioning Enhancements |
Qualcomm Incorporated |
| R1-2004652 |
Potential enhancements for NR positioning in release 17 |
Ericsson |
| 8.2.4 |
Other |
|
| R1-2003430 |
Discussion on power consumption model for NR positioning enhancements |
vivo |
| R1-2003643 |
Discussion of NLOS IIoT channel modelling for NR positioning enhancement |
CATT |
| R1-2003909 |
Uplink Transmission Based Relative Positioning |
Samsung |
| R1-2004066 |
Analysis of NR Positioning for IIOT Scenarios |
OPPO |
| R1-2004609 |
Discussion of sidelink positioning |
Huawei, HiSilicon |
| R1-2004653 |
PRS separation based on Cyclic shifts |
Ericsson |
| 8.3 |
Study on Support of Reduced Capability NR Devices |
|
| R1-2003288 |
TR skeleton for Redcap |
Ericsson |
| R1-2004731 |
Email discussion for Study on support of reduced capability NR devices |
Moderator (Ericsson) |
| R1-2004860 |
Email discussion for TR skeleton for Study on support of reduced capability NR devices |
Moderator (Ericsson) |
| R1-2004962 |
Skeleton of TR38.875 - Study on support of reduced capability NR devices |
Ericsson |
| R1-2004993 |
Email discussion for TR skeleton for Study on support of reduced capability NR devices |
Moderator (Ericsson) |
| R1-2005048 |
Email discussion summary#2 for Study on support of reduced capability NR devices |
Moderator (Ericsson) |
| R1-2005114 |
Email discussion summary#3 for Study on support of reduced capability NR devices |
Moderator (Ericsson) |
| 8.3.1 |
Potential UE complexity reduction features |
|
| R1-2003281 |
Analysis of complexity reduction features for RedCap UEs |
Futurewei |
| R1-2003289 |
Potential UE complexity reduction features for Redcap |
Ericsson |
| R1-2003301 |
Potential UE complexity reduction features |
Huawei, HiSilicon |
| R1-2003307 |
Potential UE complexity reductiton features |
China Unicom |
| R1-2003344 |
Reduced Capability UE Complexity Reduction Features |
Sierra Wireless, S.A. |
| R1-2003431 |
Capability and complexity reduction for Reduced Capability NR devices |
vivo, Guangdong Genius |
| R1-2003644 |
Discussion on potential UE complexity reduction features |
CATT |
| R1-2003687 |
On complexity reduction features for NR RedCap UEs |
MediaTek Inc. |
| R1-2003770 |
On potential UE complexity reduction features |
Intel Corporation |
| R1-2003801 |
Discussion on potential UE complexity reduction features |
ZTE |
| R1-2003828 |
On UE complexity reduction features |
Lenovo, Motorola Mobility |
| R1-2003910 |
UE complexity reduction |
Samsung |
| R1-2003922 |
View on reduced capability NR devices |
NEC |
| R1-2003934 |
UE complexity reduction features |
Nokia, Nokia Shanghai Bell |
| R1-2003966 |
Discussion on UE complexity reduction |
CMCC |
| R1-2003995 |
Discussion on potential UE complexity reduction features |
Spreadtrum Communications |
| R1-2004021 |
Discussion on potential UE complexity reduction features |
LG Electronics |
| R1-2004104 |
Discussion on UE complexity reduction |
OPPO |
| R1-2004172 |
Potential UE complexity reduction features |
TCL Communication Ltd. |
| R1-2004193 |
On potential UE complexity reduction features for NR devices |
Sony |
| R1-2004251 |
Standard Aspects of UE complexity Reduction Features |
Apple |
| R1-2004270 |
On the effect of reducing the number of UE Rx antennas on DL capacity |
Orange |
| R1-2004306 |
Discussion on potential UE complexity reduction features |
Panasonic Corporation |
| R1-2004314 |
Complexity reduction features for reduced capability NR devices |
InterDigital |
| R1-2004335 |
Discussion on Potential UE complexity reduction features |
Sharp |
| R1-2004421 |
Potential UE complexity reduction features for RedCap |
NTT DOCOMO, INC |
| R1-2004493 |
Considerations for Complexity Reduction of RedCap Devices |
Qualcomm Incorporated |
| R1-2004506 |
Initial discussion on the complexity reduction for reduced capability device |
Xiaomi Technology |
| R1-2004536 |
Discussion on potential UE complexity reduction features |
Asia Pacific Telecom co. Ltd |
| R1-2004557 |
UE Complexity Reduction for Reduced Capability NR Devices |
Potevio |
| R1-2004595 |
On potential UE complexity reduction features |
Convida Wireless |
| 8.3.2 |
Reduced PDCCH monitoring |
|
| R1-2003290 |
Reduced PDCCH monitoring for Redcap |
Ericsson |
| R1-2003302 |
Power saving for reduced capability devices |
Huawei, HiSilicon |
| R1-2003432 |
Reduced PDCCH monitoring for Reduced Capability NR devices |
vivo, Guangdong Genius |
| R1-2003546 |
Power savings for RedCap UEs |
Futurewei |
| R1-2003645 |
Discussion on PDCCH monitoring reduction |
CATT |
| R1-2003688 |
Discussion on reduced PDCCH monitoring for NR RedCap UEs |
MediaTek Inc. |
| R1-2003711 |
View on reduced PDCCH monitoring for NR devices |
NEC |
| R1-2003771 |
On PDCCH monitoring simplifications for RedCap NR Ues |
Intel Corporation |
| R1-2003802 |
Considerations on reduced PDCCH monitoring |
ZTE |
| R1-2003911 |
Reduced PDCCH monitoring |
Samsung |
| R1-2003935 |
Reduced PDCCH monitoring |
Nokia, Nokia Shanghai Bell |
| R1-2003967 |
Discussion on PDCCH monitoring reduction for Reduced Capability NR Devices |
CMCC |
| R1-2003996 |
Discussion on reduced PDCCH monitoring |
Spreadtrum Communications |
| R1-2004022 |
Discussion on PDCCH monitoring for reduced capability NR devices |
LG Electronics |
| R1-2004105 |
Discussion on reduced monitoring for PDCCH |
OPPO |
| R1-2004173 |
Reduced PDCCH monitoring |
TCL Communication Ltd. |
| R1-2004194 |
Battery lifetime enhancement for reduced capability NR devices through reduction of PDCCH monitoring |
Sony |
| R1-2004252 |
PDCCH Monitoring for Reduced Capability Devices |
Apple |
| R1-2004302 |
Considerations on reducing PDCCH monitoring |
Fujitsu |
| R1-2004315 |
Reduced PDCCH monitoring for reduced capability NR devices |
InterDigital |
| R1-2004336 |
Reduced PDCCH monitoring for reduced capability UEs |
Sharp |
| R1-2004373 |
PDCCH monitoring at reduced capability UEs |
Motorola Mobility, Lenovo |
| R1-2004422 |
Reduced PDCCH monitoring for RedCap |
NTT DOCOMO, INC |
| R1-2004494 |
Considerations for PDCCH Monitoring Reduction and Power Saving of RedCap Devices |
Qualcomm Incorporated |
| R1-2004507 |
Initial discussion on the reduced PDCCH monitoring for reduced capability devices |
Xiaomi Technology |
| R1-2004508 |
Initial discussion on the reduced PDCCH monitoring for reduced capability devices |
Xiaomi Technology |
| R1-2004509 |
Initial discussion on the reduced PDCCH monitoring for reduced capability devices |
Xiaomi Technology |
| R1-2004510 |
Initial discussion on the reduced PDCCH monitoring for reduced capability devices |
Xiaomi Technology |
| R1-2004512 |
Initial discussion on the reduced PDCCH monitoring for reduced capability devices |
Xiaomi Technology |
| R1-2004514 |
Initial discussion on the reduced PDCCH monitoring for reduced capability devices |
Xiaomi Technology |
| R1-2004541 |
Discussion on reducing PDCCH monitoring for RedCap UEs |
PANASONIC |
| 8.3.3 |
Functionality for coverage recovery |
|
| R1-2003282 |
Coverage recovery for RedCap |
Futurewei |
| R1-2003291 |
Functionality for coverage recovery for Redcap |
Ericsson |
| R1-2003303 |
Functionality for coverage recovery |
Huawei, HiSilicon |
| R1-2003433 |
Discussion on functionality for coverage recovery |
vivo, Guangdong Genius |
| R1-2003555 |
Functionality on Coverage Recovery |
Panasonic Corporation |
| R1-2003556 |
Functionality for Coverage Recovery |
Panasonic Corporation |
| R1-2003557 |
Functionality on Coverage Recovery |
Panasonic Corporation |
| R1-2003558 |
Functionality for Coverage Recovery |
Panasonic Corporation |
| R1-2003646 |
Coverage recovery for reduced capability NR devices |
CATT |
| R1-2003689 |
Discussion on coverage recovery for NR RedCap UEs |
MediaTek Inc. |
| R1-2003772 |
On coverage recovery for RedCap NR UEs |
Intel Corporation |
| R1-2003803 |
Discussion on functionality for coverage recovery |
ZTE |
| R1-2003829 |
On coverage enhancement for RedCap |
Lenovo, Motorola Mobility |
| R1-2003912 |
Coverage recovery for low capability device |
Samsung |
| R1-2003936 |
Functionality for coverage recovery |
Nokia, Nokia Shanghai Bell |
| R1-2003968 |
Consideration on coverage recovery for Reduced Capability NR Devices |
CMCC |
| R1-2003998 |
Discussion on functionality for coverage recovery |
Spreadtrum Communications |
| R1-2004023 |
Discussion on the coverage recovery of reduced capability NR devices |
LG Electronics |
| R1-2004106 |
Discussion on functionality for coverage recovery |
OPPO |
| R1-2004195 |
Coverage recovery techniques for reduced capability NR devices |
Sony |
| R1-2004253 |
Coverage recovery for reduced capability NR devices |
Apple |
| R1-2004317 |
Coverage enhancement for reduced capability NR devices |
InterDigital |
| R1-2004337 |
Coverage recovery for reduced capability UEs |
Sharp |
| R1-2004423 |
Functionality for coverage recovery for RedCap |
NTT DOCOMO, INC |
| R1-2004495 |
Considerations for Coverage Recovery of RedCap Devices |
Qualcomm Incorporated |
| R1-2004532 |
Initial discussion on coverage recovery for reduced capability |
Xiaomi Technology |
| R1-2004596 |
On coverage recovery for reduced capability UEs |
Convida Wireless |
| 8.3.4 |
Others |
|
| R1-2003283 |
Framework for RedCap UEs |
Futurewei |
| R1-2003292 |
Higher-layer aspects for Redcap |
Ericsson |
| R1-2003434 |
RRM relaxation for Reduced Capability NR devices |
vivo, Guangdong Genius |
| R1-2003647 |
Identification and access restriction for reduced capability NR devices |
CATT |
| R1-2003804 |
Discussion on UE categories for reduced capability NR devices |
ZTE |
| R1-2003913 |
Considerations on access barring and UE capability |
Samsung |
| R1-2003969 |
Discussion on framework of Reduced Capability NR Devices |
CMCC |
| R1-2003997 |
Consideration on power saving for reduced capability NR devices |
Spreadtrum Communications |
| R1-2004024 |
Consideration on the framework to support reduced capability NR devices |
LG Electronics |
| R1-2004107 |
Consideration on reduced UE capability |
OPPO |
| R1-2004176 |
Discussion on RedCap |
Sequans Communications |
| R1-2004318 |
Orthogonal ON/OFF keying for wake-up signal design |
InterDigital |
| R1-2004374 |
Narrowband operation at reduced capability UEs |
Motorola Mobility, Lenovo |
| R1-2004427 |
Capability framework for support of RedCap NR UEs |
Intel Corporation |
| R1-2004496 |
Considerations for Standardization Framework and Design Principles of RedCap Devices |
Qualcomm Incorporated |
| R1-2004535 |
On the framework and principles of Reduced Capability NR Devices |
Xiaomi Technology |
| R1-2004612 |
Other aspects for reduced capability devices |
Huawei, HiSilicon |
| 8.4 |
Study on NR coverage enhancement |
|
| R1-2003832 |
Work plan for Study on NR coverage enhancements |
China Telecom |
| R1-2003833 |
Draft skeleton of TR 38.830 Study on NR coverage enhancements |
China Telecom |
| R1-2004155 |
Overview of coverage enhancement: scenarios, channels, services and potential solutions |
Huawei, HiSilicon |
| R1-2004631 |
General Considerations for the Coverage Enhancement Study |
Ericsson |
| R1-2004753 |
Draft skeleton of TR 38.830 Study on NR coverage enhancements |
China Telecom |
| 8.4.1 |
Baseline coverage performance |
|
| R1-2003648 |
Discussion on the methodology for coverage enhancement |
CATT |
| R1-2003919 |
Assumptions for NR coverage evaluation |
vivo |
| R1-2004027 |
Discussion on evaluation for coverage enhancement |
LG Electronics |
| R1-2004377 |
Considerations for Coverage Enhancement |
Indian Institute of Tech (H) |
| R1-2004632 |
Evaluation Methodology for Coverage Enhancements |
Ericsson |
| R1-2005004 |
[101-e-NR-Cov-Enh] Email discussion on evaluation methodology and simulation assumptions for NR coverage enhancements |
Moderator (China Telecom) |
| R1-2005005 |
Unified link budget template for Rel-17 NR coverage enhancements |
Moderator (China Telecom) |
| R1-2005192 |
[101-e-Post-NR-Cov-Enh] Email discussion/approval focusing on remaining evaluation assumptions |
Moderator (China Telecom) |
| 8.4.1.1 |
FR1 |
|
| R1-2003298 |
Baseline coverage performance for FR1 |
Huawei, HiSilicon |
| R1-2003338 |
Discussion on baseline coverage performance for FR1 |
ZTE |
| R1-2003342 |
NR Coverage requirements and simulation assumption for FR1 |
Sierra Wireless, S.A. |
| R1-2003435 |
Evaluation on NR coverage performance for FR1 |
vivo |
| R1-2003464 |
Requirements for Voice coverage enhancements with FR1 |
SoftBank Corp. |
| R1-2003649 |
Discussion on the baseline performance and simulation assumptions of coverage enhancement for FR1 |
CATT |
| R1-2003683 |
Discussion on scenarios for FR1 baseline performance evaluation |
MediaTek Inc. |
| R1-2003773 |
Discussion on baseline coverage performance for FR1 |
Intel Corporation |
| R1-2003778 |
Downlink coverage in FR1 |
Charter Communications, Inc |
| R1-2003816 |
Discussion on evaluation methodologies for baseline coverage performance analysis |
Panasonic Corporation |
| R1-2003821 |
Baseline evaluation for NR UL coverage enhancement |
Lenovo, Motorola Mobility |
| R1-2003834 |
Evaluation methodology and preliminary baseline performance for NR coverage enhancements |
China Telecom |
| R1-2003914 |
Scenarios and simulation assumptions for coverage enhancement in FR1 |
Samsung |
| R1-2003940 |
Simulation Assumptions and Baseline Coverage for FR1 |
Nomor Research GmbH, Facebook |
| R1-2003970 |
Discussion on coverage enhancements in FR1 |
CMCC |
| R1-2004108 |
NR coverage performance for FR1 |
OPPO |
| R1-2004178 |
Baseline coverage evaluation of UL and DL channels – FR1 |
Nokia, Nokia Shanghai Bell |
| R1-2004196 |
On NR coverage analysis in FR1 |
Sony |
| R1-2004249 |
On baseline coverage performance for FR1 |
Apple |
| R1-2004304 |
Simulation assumptions and throughput performance for UL in FR1 |
InterDigital, Inc. |
| R1-2004338 |
Preliminary evaluation for FR1 Urban scenario |
Sharp |
| R1-2004352 |
Simulation Parameters and Initial Results for FR1 |
Ericsson |
| R1-2004424 |
Baseline coverage performance for FR1 |
NTT DOCOMO, INC |
| R1-2004497 |
Baseline FR1 coverage performance |
Qualcomm Incorporated |
| R1-2004540 |
Baseline coverage performance for FR1 |
xiaomi |
| R1-2004700 |
Preliminary evaluation for FR1 Urban scenario |
Sharp |
| R1-2004716 |
Baseline coverage performance for FR1 |
Huawei, HiSilicon |
| R1-2004937 |
Simulation Parameters and Initial Results for FR1 |
Ericsson |
| 8.4.1.2 |
FR2 |
|
| R1-2003299 |
Discussion on baseline coverage evaluation for FR2 |
Huawei, HiSilicon |
| R1-2003339 |
Discussion on baseline coverage performance for FR2 |
ZTE |
| R1-2003436 |
Evaluation on NR coverage performance for FR2 |
vivo |
| R1-2003650 |
Discussion on the baseline performance and simulation assumptions of coverage enhancement for FR2 |
CATT |
| R1-2003774 |
Discussion on baseline coverage performance for FR2 |
Intel Corporation |
| R1-2003779 |
Downlink coverage in FR2 |
Charter Communications, Inc |
| R1-2003915 |
Scenarios and simulation assumptions for coverage enhancement in FR2 |
Samsung |
| R1-2003971 |
Discussion on coverage enhancements in FR2 |
CMCC |
| R1-2004179 |
Baseline coverage evaluation of UL and DL channels – FR2 |
Nokia, Nokia Shanghai Bell |
| R1-2004197 |
Considerations on Simulation Assumptions for Coverage Enhancements for FR2 |
Sony |
| R1-2004305 |
Simulation assumptions for UL in FR2 |
InterDigital, Inc. |
| R1-2004353 |
Simulation Parameters and Initial Results for FR2 |
Ericsson |
| R1-2004425 |
Baseline coverage performance for FR2 |
NTT DOCOMO, INC |
| R1-2004498 |
Baseline FR2 coverage performance |
Qualcomm Incorporated |
| R1-2004758 |
Evaluation on NR coverage performance for FR2 |
vivo |
| 8.4.2 |
Potential techniques for coverage enhancements |
|
| R1-2003300 |
Potential solutions for coverage enhancement |
Huawei, HiSilicon |
| R1-2003340 |
Discussion on potential techniques for coverage enhancements |
ZTE |
| R1-2003343 |
Potential techniques for NR coverage enhancements |
Sierra Wireless, S.A. |
| R1-2003437 |
Discussion on potential techniques for coverage enhancements |
vivo |
| R1-2003651 |
Discussion on the method for coverage enhancement |
CATT |
| R1-2003775 |
Discussion on potential techniques for NR coverage enhancement |
Intel Corporation |
| R1-2003817 |
Discussion on potential techniques for coverage enhancements |
Panasonic Corporation |
| R1-2003835 |
Potential solutions for PUSCH coverage enhancements |
China Telecom |
| R1-2003916 |
Considerations on potential techniques for coverage enhancement |
Samsung |
| R1-2003938 |
Potential Solutions on Coverage Enhancement for FR1 |
Nomor Research GmbH, Facebook |
| R1-2004028 |
Discussion on potential techniques for coverage enhancement |
LG Electronics |
| R1-2004109 |
The potential solutions to enhance NR coverage |
OPPO |
| R1-2004180 |
Discussion on possible approaches and solutions for NR coverage enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2004198 |
Techniques for NR coverage enhancement |
Sony |
| R1-2004250 |
On potential techniques for coverage enhancement |
Apple |
| R1-2004273 |
Potential techniques for coverage enhancements |
InterDigital, Inc. |
| R1-2004354 |
Potential Areas for Coverage Enhancement |
Ericsson |
| R1-2004426 |
Potential techniques for coverage enhancements |
NTT DOCOMO, INC |
| R1-2004499 |
Potential techniques for coverage enhancement |
Qualcomm Incorporated |
| 8.4.3 |
Other |
|
| R1-2003341 |
Discussion on evaluation methodology for NR coverage |
ZTE |
| R1-2003438 |
Discussion on coverage evaluation assumptions and performance for RedCap UE |
vivo |
| R1-2003652 |
Preliminary simulation results for different channels |
CATT |
| R1-2003776 |
Discussion on simulation assumption for NR coverage enhancement |
Intel Corporation |
| R1-2003917 |
Preliminary results for VoIP service in TDD |
Samsung |
| R1-2004181 |
Evaluation assumptions for NR coverage enhancement evaluation |
Nokia, Nokia Shanghai Bell |
| R1-2004355 |
Coverage Enhancements: Four BS Antennas at Low Band |
Ericsson |
| R1-2004610 |
System-level simulation assumptions and evaluation metrics for coverage enhancement |
Huawei, HiSilicon |
| 8.5 |
Other |
|
| R1-2003560 |
Discussion on the enhancement of NTN |
ZTE |
| R1-2003667 |
Evaluations and observations for R17 UE power saving enhancements |
MediaTek Inc. |
| R1-2003918 |
On Rel.17 FeMIMO WI |
Samsung |
| R1-2004246 |
Considerations on HARQ/CSI enhancements |
Apple |
| R1-2004269 |
Discussion on Rel 17 NR FeMIMO |
Nokia, Nokia Shanghai Bell |
| R1-2004602 |
On Sidelink enhancement |
Huawei, HiSilicon |
| R1-2004633 |
High Level Views on Rel-17 feMIMO |
Ericsson |